Skip to main content
Glama

Submit by Hand

Order progress

get_order_status
Read-only

Progress of an order: paid or not, how many submissions are done, in review, live or declined, the delivery date, and the next step for the user. Takes the order_url from create_order (also emailed to the buyer).

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": {
      "order_url": "<order_url>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_urlYeshttps://submitbyhand.com/o/<token>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds substantive behavioral value by enumerating the returned status fields despite no output schema, though it does not mention whether results are a point-in-time snapshot or how stale data might be.

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?

Two sentences, both earning their place: the first front-loads the returned fields, the second gives parameter provenance. No filler or repetition.

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?

Given a single required parameter, full schema documentation, safety annotations, and no output schema, the description is nearly complete because it enumerates the result fields. Minor gaps are that it does not clarify snapshot semantics or privacy considerations for the token URL.

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

Parameters4/5

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

Schema coverage is 100% and already documents the URL format, but the description adds meaning beyond the schema by explaining where to obtain the order_url and that it is emailed to the buyer.

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 enumerates exactly what progress information is returned: payment status, submission counts by state, delivery date, and next step. This clearly distinguishes it from sibling tools like create_order or get_pricing.

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?

Explains that order_url comes from create_order and is also emailed to the buyer, giving clear context for when to use it. It does not explicitly state exclusions or alternatives, but for a simple read-by-URL tool no meaningful alternative is apparent.

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