Skip to main content
Glama

IRLsend Postcards

Check a postcard order

check_postcard_order
Read-onlyIdempotent

Check where a postcard made with design_postcard is: not ordered yet, waiting for payment, paid and going to print, mailed (with the expected delivery date when known), or refunded. Takes the card code.

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": {
      "code": "<code>"
    },
    "name": "check_postcard_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe card code from design_postcard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 elsewhere. The description adds real value by disclosing the result states and that a delivery date is included when known — behavior the annotations cannot express, especially with no output schema.

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 status enumeration and compact at two sentences, with no filler. The inline list of states is dense but each item carries information an agent needs to interpret the response.

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 one-parameter read tool with no output schema, the description supplies the essential missing piece — what states and fields come back. It stops short of covering error behavior for an invalid or unknown card code, which would complete the picture.

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%: the single 'code' parameter is documented with its origin and a regex pattern. The description's 'Takes the card code' merely restates the schema's own description, adding no format or lookup semantics beyond it. Baseline 3 applies.

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?

Names a specific verb (check status) and resource (postcard order) and enumerates the exact states returned: not ordered, waiting for payment, paid/printing, mailed with delivery date, refunded. It also ties the tool to design_postcard as the origin of the card, which distinguishes it from the creation sibling.

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?

Usage is only implied: the phrase 'made with design_postcard' signals this is a follow-up to card creation. There is no explicit when-to-use statement, no exclusion, and no guidance on what to do if the code is unknown or the order is absent.

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