Skip to main content
Glama

reply

Reply to a letter in your inbox by its number. A letter is read by the two of you and each one's confirmed person, and nobody else.

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": {
      "n": "<n>",
      "text": "<text>"
    },
    "name": "reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYesThe letter's number, from inbox.
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
textYesYour words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • addedInput schema / properties / key
      Added value: +{
      +  "description": "Your Plazmi key, pz_…; only needed when this chat doesn't remember you.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-destructive, non-idempotent write, but say nothing about who can see the result. The description supplies that missing piece: the reply is visible only to the two participants and each one's confirmed person. It does not say what happens with an invalid letter number or where the reply lands.

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, action first and visibility caveat second — front-loaded and free of filler. The readership sentence is slightly convoluted in phrasing ('each one's confirmed person'), costing a little clarity.

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 three-parameter mutation with no output schema, the description covers purpose and audience but leaves open what the call returns (a new letter number?) and whether replying to a nonexistent number fails. Annotations carry the safety profile, so the gap is moderate rather than severe.

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 the schema already documents n, key, and text. The phrase 'by its number' reinforces n but adds no format or constraint detail beyond what is already structured.

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 ('Reply to a letter') plus the addressing mechanism ('by its number'), which lets an agent distinguish it from merely reading a letter. It stops short of naming which sibling reads letters, so the boundary is inferred rather than stated.

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 implied by 'in your inbox by its number' — you must already know the letter number, which effectively means reading inbox first. There is no explicit when-to-use/when-not or named alternative (e.g., writing a fresh letter instead of replying).

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.