Narrareach

Decide voice suggestion

decide_voice_suggestion

Record the writer's answer to one suggestion from get_voice_profile. Ask the writer first and call this only after they answer: "approve" adds it as a rule (pass text if they reword it), "dismiss" means they said no, "later" asks again in a week. One suggestion per call. Never decide for the writer.

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": {
      "suggestionId": "<suggestionId>",
      "decision": "<decision>"
    },
    "name": "decide_voice_suggestion"
  }
}

Input Schema

Name	Required	Description
`text`	No	Only with "approve": the rule in the writer's own wording, if they changed it.
`writer`	No	Optional team writer name, handle, or id within the workspace. "me" selects your linked voice. Requires workspace.
`decision`	Yes	What the writer said.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user's personal account.
`suggestionId`	Yes	The suggestion id from get_voice_profile.

Output Schema

Name	Required	Description	Default
`undo`	Yes
`status`	Yes
`decision`	Yes
`ruleCount`	Yes
`connectedAccount`	No
`suggestionsRemaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare that this is not read-only, not idempotent, and not destructive. The description adds useful behavioral context beyond that: 'approve' creates a rule, 'later' defers for a week, and only one suggestion can be decided per call. It does not cover permissions or auth requirements, but it adds meaningful workflow behavior.

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?

The description is compact and front-loaded: it names the action first, then gives usage rules and decision semantics. Every sentence contributes directly to correct invocation.

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?

Given the rich schema, annotations, and output schema, the description provides everything an agent needs to call this tool correctly. It covers when to call, how to interpret decisions, one-per-call behavior, and the do-not-decide-for-the-writer constraint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 each parameter. The description still adds semantic value by clarifying that text is only used with 'approve' and only when the writer rewords the rule, and by explaining the behavioral effect of each decision enum. It does not add much for writer/workspace 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 states a specific verb and resource: 'Record the writer's answer to one suggestion from get_voice_profile.' It distinguishes the tool from siblings by tying it directly to the suggestion workflow and clarifying that it records one decision per call.

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?

It gives explicit usage conditions: ask the writer first, call only after they answer, and never decide for the writer. It also defines what each decision value means in workflow terms, leaving no ambiguity about when this tool is appropriate.

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

All Narrareach tools Inspect

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

Need Help?