FinancialMD

Status of a data request

request_status

Read-onlyIdempotent

The status of a data request sent with request_data: new (received), triaged (reviewed), planned, done (with the endpoint or tool that now serves it) or wontfix (with a note, for example data that only licensed feeds carry). Pass the request_id request_data returned. Use it to follow a request until it ships. Also gives how many requests and distinct requesters the item has. Free, no key.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_id": "0b8f6a52-6f0e-4a8e-9a43-3c0f6b2d1e11"
    },
    "name": "request_status"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes	The request_id request_data returned (a uuid). A demand item id works too.

Output Schema

Name	Required	Description
`data`	No	{ item_id, title, status, public_note, served_by, requests, requesters, ... }: the demand item the request belongs to.
`meta`	No	Request metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
`error`	No	Present only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by explaining what each status means and, importantly, that 'done' carries the endpoint/tool that now serves the data and 'wontfix' carries a note, plus 'Free, no key' which discloses the auth/cost profile. It does not describe error behavior for an unknown id, keeping it at a solid 3 rather than a 4.

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

Conciseness4/5

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

Front-loaded with the core purpose and packed with useful detail in a compact form; the parenthetical glosses on each status earn their place. Slightly dense with nested parentheses, but there is no filler.

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

Completeness4/5

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

For a single-parameter read tool with full schema coverage, annotations and an output schema, the description supplies everything an agent needs to decide and call: provenance of the id, status vocabulary, and the fact that per-item demand counts are also returned. The only minor gap is unspecified behavior for an invalid or unknown request_id.

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 coverage is 100%, including the UUID pattern and the note that a demand item id is also accepted, so the schema already does the heavy lifting. The description adds provenance ('the request_id request_data returned'), which is useful but marginal, matching the baseline 3.

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?

States a specific resource and the exact operation (returning the status of a data request created by request_data), and enumerates the possible status values so the agent immediately knows what the response space looks like. This clearly distinguishes it from the sibling request_data, which creates rather than reports.

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

Usage Guidelines4/5

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

Explicitly says how to obtain the input ('Pass the request_id request_data returned') and when to use it ('to follow a request until it ships'), naming the companion tool. It stops short of stating when *not* to use it or what to do if the id is unknown, so it is strong but not fully exhaustive.

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

All FinancialMD tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?