Narrareach

Remove voice material

remove_voice_material

DestructiveIdempotent

Remove one item from the writer's material bank, when the writer asks you to drop it. Use the material id from get_voice_profile (pass detail "full" to see every item). The writer can undo it.

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": {
      "materialId": "<materialId>"
    },
    "name": "remove_voice_material"
  }
}

Input Schema

Name	Required	Description
`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.
`materialId`	Yes	The material id from get_voice_profile.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered; the description adds the genuinely new behavioral fact that the removal is reversible ("The writer can undo it"), which no annotation conveys. Permissions/scope behavior is still left to 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 short sentences, action and scope front-loaded, with the undo note as a useful trailer; no sentence 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?

Output schema exists so return values need not be described, all three params are schema-documented, and the description covers purpose, trigger, id source, and reversibility. Nothing needed to call it correctly is missing.

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, but the description adds an actionable tip beyond the schema by telling the agent to pass detail "full" to get_voice_profile in order to see every item's id. writer and workspace semantics are left entirely to 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?

States a specific verb (Remove) and resource (one item from the writer's material bank), and the singular scope distinguishes it from add_voice_material and remove_voice_rule without opening any 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?

Gives a clear trigger condition ("when the writer asks you to drop it") and routes the agent to get_voice_profile for the id, but does not explicitly contrast this with the nearest alternatives such as remove_voice_rule.

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?