Skip to main content
Glama
edithatogo

fyi-mcp

by edithatogo
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Update Request

update_request
Idempotent

Update an existing local FYI request by ID, fully replacing title, body, and optional fields. Marks the record dirty for offline sync.

Instructions

Replace editable fields on an existing local FYI/Alaveteli request by ID and mark the record dirty for offline sync. Use when the request already exists and fields changed; use create_request for a new ID and delete_request to remove. Requires id, title, and body (full replacement for those fields, not a sparse patch). Mutating but non-destructive; safe to re-run with the same values; does not call remote APIs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExisting local request ID to update (must already exist).
urlNoOptional replacement absolute FYI/Alaveteli URL.
bodyYesReplacement request body or draft text (required; full replace).
tagsNoOptional full replacement tag list (not appended to existing tags).
titleYesReplacement request title (required; full replace, not merge).
statusNoOptional replacement local lifecycle status; changing status does not submit or withdraw a remote request.
user_nameNoOptional replacement requester display name; when omitted, existing local value is preserved.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesThe updated local request record.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changedv0.1.1
    • changedInput schema / properties / body / description
      Previous value: -"The request body."New value: +"Replacement request body or draft text (required; full replace)."
    • addedInput schema / properties / body / minLength
      Added value: +1
    • changedInput schema / properties / id / description
      Previous value: -"The request ID."New value: +"Existing local request ID to update (must already exist)."
    • addedInput schema / properties / id / minimum
      Added value: +1
    • changedInput schema / properties / status / description
      Previous value: -"Status of the request."New value: +"Optional replacement local lifecycle status; changing status does not submit or withdraw a remote request."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "draft",
+  "submitted",
+  "waiting_response",
+  "successful",
+  "partially_successful",
+  "refused",
+  "overdue",
+  "clean",
+  "dirty",
+  "pending",
+  "conflict"
+]
    • changedInput schema / properties / tags / description
      Previous value: -"Optional list of tags."New value: +"Optional full replacement tag list (not appended to existing tags)."
    • changedInput schema / properties / title / description
      Previous value: -"The request title."New value: +"Replacement request title (required; full replace, not merge)."
    • addedInput schema / properties / title / minLength
      Added value: +1
    • changedInput schema / properties / url / description
      Previous value: -"The URL on Alaveteli or FYI."New value: +"Optional replacement absolute FYI/Alaveteli URL."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • changedInput schema / properties / user_name / description
      Previous value: -"Name of the user."New value: +"Optional replacement requester display name; when omitted, existing local value is preserved."
    • addedOutput schema / properties / request / additionalProperties
      Added value: +false
    • addedOutput schema / properties / request / description
      Added value: +"The updated local request record."
    • addedOutput schema / properties / request / properties
      Added value: +{
+  "body": {
+    "description": "Request body or draft correspondence text.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "created_at": {
+    "description": "ISO-8601 creation timestamp when recorded.",
+    "format": "date-time",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "id": {
+    "description": "Stable local request identifier.",
+    "minimum": 1,
+    "type": "integer"
+  },
+  "status": {
+    "description": "Current Alaveteli/FYI request lifecycle status.",
+    "enum": [
+      "draft",
+      "submitted",
+      "waiting_response",
+      "successful",
+      "partially_successful",
+      "refused",
+      "overdue",
+      "clean",
+      "dirty",
+      "pending",
+      "conflict",
+      null
+    ],
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "tags": {
+    "description": "Optional local tags attached to the request.",
+    "items": {
+      "type": "string"
+    },
+    "type": [
+      "array",
+      "null"
+    ]
+  },
+  "title": {
+    "description": "Public title of the official information request.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "updated_at": {
+    "description": "ISO-8601 update timestamp used for ordering and sync.",
+    "format": "date-time",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "url": {
+    "description": "Canonical public request URL when available.",
+    "format": "uri",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "user_name": {
+    "description": "Requester display name when known.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedOutput schema / properties / request / required
      Added value: +[
+  "id",
+  "title",
+  "body"
+]
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds context: 'mark the record dirty for offline sync', 'mutating but non-destructive', and 'does not call remote APIs', which enriches understanding beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with efficient front-loading: first sentence states action, then usage guidelines, parameter semantics, and behavioral notes. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, 3 required, and an output schema, the description covers purpose, usage, parameter behaviors, and side effects (dirty marking, no remote calls). It is complete for an AI agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds crucial semantics: 'full replacement for those fields, not a sparse patch' for title/body, 'not appended to existing tags' for tags, and 'changing status does not submit or withdraw a remote request' for status. This goes well beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies 'Replace editable fields on an existing local FYI/Alaveteli request by ID and mark the record dirty for offline sync', which clearly states the verb, resource, and scope. It also distinguishes from siblings by mentioning create_request for new ID and delete_request for removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'Use when the request already exists and fields changed', and provides alternatives: 'use create_request for a new ID and delete_request to remove'. Also notes it is safe to re-run with same values.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/edithatogo/fyi-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server