Skip to main content
Glama

Niche of One Network

Write to J.D.

reply_to_jd

Members. Send a note to J.D. Forrest. A person reads it; nothing answers it automatically. Shows a preview first; call again with confirm true and the preview_token it returned to commit.

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": {
      "message": "<message>"
    },
    "name": "reply_to_jd"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave out for a preview. true commits, with the preview_token.
messageYes
subjectNo
preview_tokenNoThe preview_token the preview returned. Needed with confirm true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the two-step preview/commit protocol and that a preview_token must be carried into the confirming call — critical behavior an agent would otherwise stumble into. It also implies a membership gate ("Members.") and human review. It omits rate limits, failure behavior, and what the preview contains.

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?

Three short sentences, front-loaded with the recipient and the key safety mechanism. The leading "Members." is an unanchored fragment that wastes a slot where a proper first clause could sit, but otherwise there is no filler.

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 4-parameter, non-idempotent write tool with no output schema, the description covers the essential confirmation workflow and the human-delivery model. It leaves gaps around membership verification, what the preview returns, and post-commit behavior, but nothing required to invoke it correctly is missing.

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?

With 50% schema description coverage, the two undocumented parameters are message and subject; the description does not add guidance on what to put in them or what subject defaults to. It does usefully clarify the interplay of confirm and preview_token, which the schema only describes individually.

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 recipient: "Send a note to J.D. Forrest." The resource is unambiguous and clearly a direct message to a named person rather than a public post or saved draft. It does not explicitly differentiate from siblings like post_to_underground or save_to_onewriter, so it stops short of a 5.

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?

"A person reads it; nothing answers it automatically" hints at when this is appropriate (human correspondence, not an automated query), but there is no explicit when-to-use versus the sibling tools and no stated prerequisites beyond the leading "Members." fragment. Usage is implied rather than instructed.

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