Skip to main content
Glama
Sign In

ReputeMap

by com.reputemap
OverviewDiscussionsAdmin

Draft reply variants

draft_reply
Destructive

Generate 2-3 reply drafts for one review using ReputeMap's tuned generator (the same one the app uses, with the business's saved voice and sign-off), and save the draft so it appears in the app's editor. NEVER publishes anything - drafts only.

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": {
      "review_id": "<review_id>"
    },
    "name": "draft_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYesUUID from list_reviews
instructionsNooptional one-off guidance for this draft, e.g. 'mention the new units' or 'keep it under 40 words'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / instructions
      Added value: +{
+  "description": "optional one-off guidance for this draft, e.g. 'mention the new units' or 'keep it under 40 words'",
+  "maxLength": 300,
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely non-obvious context: the same tuned generator the app uses, the business's saved voice and sign-off, and that the draft is persisted into the app editor. It does not clarify whether an existing draft is overwritten (which is what the destructive hint likely refers to) or whether repeated calls regenerate variants.

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 load-bearing, with the primary action and its persistence effect front-loaded and the safety guarantee last. No filler or restatement of the tool name.

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?

Covers action, persistence destination, and the no-publish guarantee for a two-parameter mutation tool with no output schema. The remaining gap is what the caller receives back and whether an existing draft is replaced, which matters given destructiveHint=true.

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 description coverage is 100%, so review_id's provenance ('UUID from list_reviews') and instructions' format and 300-char cap are already documented in the schema. The description adds only that drafting is scoped to 'one review', which is a baseline contribution when the schema does the heavy lifting.

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 verb (generate), resource (reply drafts), and scope (one review), plus where the result goes ('appears in the app's editor'). It is immediately distinguishable from publish_reply by the explicit 'drafts only' clause.

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?

The 'NEVER publishes anything - drafts only' line clearly establishes this as the pre-publish step, which routes the agent away from publish_reply. It stops short of naming publish_reply as the follow-up tool, so the when-to-use guidance is clear but not fully explicit about the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ReputeMap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources