Skip to main content
Glama
edithatogo

fyi-mcp

by edithatogo
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Retrieve Request

retrieve_request
Read-onlyIdempotent

Retrieve a single tracked request and its correspondence by ID. Use after listing requests to get full text and history for one request.

Instructions

Retrieve one locally tracked FYI/Alaveteli request and its stored correspondence by request ID. Use after list_requests when you need full text/history for a single request; do not use for bulk listing (list_requests) or database health (check_status). Read-only and idempotent; fails if the ID is missing; never contacts remote sites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStable local request ID to load (must already exist; typically from list_requests).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesThe requested FYI/Alaveteli request record.
correspondenceYesStored correspondence items linked to the request, in database order.

Schema Changelog

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

  1. Changed11 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"The unique request ID."New value: +"Stable local request ID to load (must already exist; typically from list_requests)."
    • addedInput schema / properties / id / minimum
      Added value: +1
    • addedOutput schema / properties / correspondence / description
      Added value: +"Stored correspondence items linked to the request, in database order."
    • addedOutput schema / properties / correspondence / items / additionalProperties
      Added value: +false
    • addedOutput schema / properties / correspondence / items / description
      Added value: +"A correspondence item associated with an FYI request."
    • addedOutput schema / properties / correspondence / items / properties
      Added value: +{
+  "attachments": {
+    "description": "Optional attachment URLs or identifiers linked to the correspondence.",
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "type": [
+      "array",
+      "null"
+    ]
+  },
+  "body": {
+    "description": "Message body or extracted correspondence text.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "direction": {
+    "description": "Whether the correspondence was sent by the requester or received as an authority response.",
+    "enum": [
+      "request",
+      "response"
+    ],
+    "type": "string"
+  },
+  "sent_at": {
+    "description": "ISO-8601 sent timestamp when captured.",
+    "format": "date-time",
+    "type": "string"
+  },
+  "state": {
+    "description": "Optional Alaveteli correspondence state when captured.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedOutput schema / properties / correspondence / items / required
      Added value: +[
+  "direction",
+  "body",
+  "sent_at"
+]
    • addedOutput schema / properties / request / additionalProperties
      Added value: +false
    • addedOutput schema / properties / request / description
      Added value: +"The requested FYI/Alaveteli 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.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. Description adds 'fails if the ID is missing' and 'never contacts remote sites', which are useful beyond annotations. However, the core behavioral traits (read-only, idempotent) are redundant with annotations, preventing a 5.

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?

Three concise sentences, front-loaded with the core purpose, no wasted words. Every sentence adds distinct value: purpose, usage guidance, and behavioral transparency.

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?

For a simple retrieval tool with one parameter and an existing output schema, the description covers all necessary aspects: what it does, when to use, failure behavior, and safety profile. No gaps.

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

Parameters3/5

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

Schema description coverage is 100%, and the parameter description in the schema is already clear ('Stable local request ID to load...'). The tool description does not add new parameter-level information beyond reinforcing the ID usage context. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Retrieve' and resource 'one locally tracked FYI/Alaveteli request and its stored correspondence by request ID'. It explicitly distinguishes from sibling tools like list_requests and check_status, meeting the high standard for purpose clarity.

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 ('after list_requests when you need full text/history for a single request'), when not to use ('do not use for bulk listing or database health'), and names alternatives (list_requests, check_status). This is exemplary guidance.

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