Skip to main content
Glama

read_merchant_work_execution

Read the linked execution for a proposal selected from this seller. Requires merchant:work bearer authentication.

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": {
      "requestId": "<requestId>"
    },
    "name": "read_merchant_work_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose a concrete operational requirement — merchant:work bearer authentication — which is real value beyond structured data. However, it says nothing about failure modes (missing execution, unselected proposal), whether the call is side-effect free, or what happens with a stale requestId.

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 sentences, no filler, with the resource statement front-loaded and the auth requirement trailing as a constraint. It is arguably over-terse for the ambiguity it leaves, but nothing written is wasted.

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

Completeness3/5

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

For a one-parameter read tool with no output schema and no annotations, the definition covers what to fetch and the auth requirement but omits the return shape (what fields an 'execution' exposes) and error behavior. Minimal but not complete given there is no output schema to defer to.

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 is 0% and the single parameter requestId is never mentioned in the description, so the agent gets no meaning beyond the schema's uuid format and pattern. The phrase 'proposal selected from this seller' hints at what the identifier resolves to but does not explicitly link requestId to a proposal or explain where the agent obtains it.

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

Purpose4/5

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

States a specific verb and resource ('Read the linked execution') plus a scoping qualifier ('for a proposal selected from this seller'), so the agent knows the object being fetched. It does not differentiate from the near-identical sibling 'read_work_execution', leaving ambiguity about which read applies to which state.

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

Usage Guidelines2/5

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

The description gives a precondition (the proposal must already be selected from this seller) but no guidance on when to pick this tool over read_work_execution or read_work_ticket_result. There are no exclusions, no ordering advice, and no statement of what happens if the execution does not exist yet.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources