Skip to main content
Glama

IRLsend Postcards

Change a postcard

revise_postcard
Destructive

Make a new version of a postcard designed with design_postcard: the same card code and link, changed as asked (for example a different color, drawing or wording). The new version replaces the current one on the card page. Only for a card that is not paid for yet. Do not include any street address, phone number or email.

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>",
      "change_request": "<change_request>"
    },
    "name": "revise_postcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe card code from design_postcard.
sign_offNoOnly when the person asks for a new sign-off, exactly as they want it, e.g. "Best, Sam".
change_requestYesWhat to change, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the previous version is replaced on the card page while the card code and link stay the same, and the operation is blocked on paid cards. It does not describe what is returned or what happens on a rejected change request, but the mutation semantics and preconditions are well disclosed.

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?

Three short sentences, front-loaded with the core action, then the replacement effect, then the eligibility and content limits. No sentence is redundant and nothing is buried.

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 three-parameter mutation with no output schema, the description covers the essentials an agent needs: the upstream dependency, the precondition, the replacement behavior, and a PII prohibition. The remaining gap is return/error behavior, which is minor given the annotations and simple schema.

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%, so code, sign_off and change_request are already documented, giving a baseline of 3. The description adds modest meaning by framing change_request as plain-word changes with examples (color, drawing, wording) and by implying sign_off is optional-only-when-asked, but it does not add format or constraint detail beyond the schema.

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?

The description uses a specific verb and resource ("Make a new version of a postcard") and anchors it to the sibling that produces the input ("designed with design_postcard"), including the shared card code and link. An agent can distinguish this from creating a fresh card or checking an order without opening any schema.

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?

It states a clear precondition ("Only for a card that is not paid for yet") and a hard content exclusion (no street address, phone number or email), plus the upstream tool that must have run first. It stops short of naming what to do instead when the card is already paid, so the exclusion is stated without a routing alternative.

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