Narrareach

Update voice rule

update_voice_rule

Idempotent

Reword one rule in the writer's voice profile, when the writer asks you to change it. Use the rule id from get_voice_profile. Style only: a rule cannot allow invented facts, stories, quotes, or numbers.

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": {
      "ruleId": "<ruleId>",
      "text": "<text>"
    },
    "name": "update_voice_rule"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The new wording, as the writer wants it.
`ruleId`	Yes	The rule id from get_voice_profile.
`writer`	No	Optional team writer name, handle, or id within the workspace. "me" selects your linked voice. Requires workspace.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user's personal account.

Output Schema

Name	Required	Description	Default
`undo`	Yes
`changed`	Yes
`ruleCount`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this is a write (readOnlyHint=false) that is idempotent and non-destructive, so the safety profile is covered. The description adds a genuine content constraint not present in structured data: rules are style-only and may not permit invented facts, stories, quotes, or numbers. It does not discuss auth/workspace permissions beyond the schema.

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?

Three sentences, front-loaded with the action and scope, then trigger and id source, then the content constraint. No filler or repetition of schema/annotation data.

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?

With an output schema covering returns and annotations covering the safety profile, the description supplies purpose, trigger, id source, and a content constraint. It omits whether the edit is reversible (undo_voice_change exists), a minor gap rather than a blocking one.

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 baseline is 3. The description goes beyond it by telling the agent where ruleId originates (get_voice_profile) and by constraining the text parameter to style-only wording, adding meaning the schema's maxLength/description does not convey.

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 (Reword) and resource (one rule in the writer's voice profile), and the singular scope distinguishes it from siblings like add_voice_material and remove_voice_rule. An agent can tell what it does without opening the schema.

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?

"when the writer asks you to change it" gives a clear trigger condition, and it points to get_voice_profile as the source of the rule id. It stops short of naming explicit exclusions (e.g. use remove_voice_rule to delete, add_voice_material to append), so it is clear context without full alternative routing.

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?