Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Draft review replies

draft_review_replies
Idempotent

Get suggested replies to one review, in three tones: warm, professional and brief. The first call for a review generates the drafts with an AI model, using the workspace's customer support voice when one is set up, and saves them on the review; later calls return the saved drafts. Drafts for reviews of 1 or 2 stars are marked as needing a careful read before sending.

Input: review_id from list_reviews_to_reply. Nothing is posted. Show the drafts to the user, let them pick or edit one, then call send_review_reply with the final text.

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

Input Schema

NameRequiredDescriptionDefault
review_idYesThe review id from list_reviews_to_reply.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Discloses behavior well beyond the annotations: the first call generates drafts with an AI model using the workspace's support voice, later calls return saved drafts, and low-star reviews get a 'needs careful read' marker. This explains the non-obvious side effect (drafts are persisted on the review) that readOnlyHint=false implies but does not articulate.

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?

The generation-vs-cached distinction is front-loaded and the workflow sentence is compact and actionable. A few clauses (the tone list, the voice sentence) could be trimmed, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still tells the agent what comes back (three tonal drafts plus a caution marker) and what to do with them next. Nothing needed to invoke it correctly or interpret its result 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?

Schema coverage is 100%, and the description only restates where review_id comes from, which the schema already documents. With the schema carrying the parameter burden, this meets the baseline without adding new meaning.

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?

Opens with a specific verb and resource ('Get suggested replies to one review') and immediately scopes the output ('three tones: warm, professional and brief'). It is clearly distinguishable from send_review_reply, which is named later as the follow-on action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the required input source ('review_id from list_reviews_to_reply') and the exact workflow: show drafts, let the user pick or edit, then call send_review_reply with final text. The boundary against the sibling is explicit ('Nothing is posted'), leaving no ambiguity about when to use which tool.

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

All Blaze 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