Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_operation_status

Check a durable request's status and reconcile outcomes without repeating the mutation; a timeout does not mean cancellation.

Instructions

Read/reconcile a durable request without repeating the mutation. Timeout never means cancelled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_id": "<request_id>"
    },
    "name": "md_operation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does add genuinely useful semantics — the request is durable, reads are non-mutating, and a timeout does not imply cancellation — but it omits whether the call blocks, what status values are returned, and how errors or unknown request_ids are handled.

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?

Two short sentences with no filler, and the key timeout semantics are front-loaded. The terseness borders on cryptic, but nothing is wasted.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should explain what a status response looks like and how to act on pending versus completed states. It also fails to say how request_id is obtained, leaving the agent without enough to interpret results.

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

Parameters2/5

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

Schema description coverage for request_id is 0%, so the description is the only place to explain where the id comes from, its format, and its lifetime. The description never mentions request_id at all, leaving the sole parameter undocumented beyond its name.

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

Purpose3/5

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

The description identifies the resource as a 'durable request' and the action as 'read/reconcile', but never states plainly that this retrieves the status of a previously submitted operation by request_id. 'Reconcile' is ambiguous and overlaps with sibling names like md_reconcile_property_operation, so an agent cannot cleanly distinguish purposes from the text alone.

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

Usage Guidelines3/5

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

'Without repeating the mutation' and 'Timeout never means cancelled' imply the use case: check an in-flight request after a timeout instead of retrying the write. However, there is no explicit routing instruction naming alternatives or stating when this should not be used.

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

Deploy Server

Other Tools