Skip to main content
Glama

Analyze voice drift (VIP)

analyze_voice_drift
Read-onlyIdempotent

VIP. Compares what the bot drafted with what the owner really sent, and returns the Never rules to add to voice.md. An edit seen in two or more pairs becomes a permanent rule (the Two-Edit Rule). Without a member token it returns a labeled demo on sample drafts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_voice_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsNoDraft and sent pairs from the last week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context the annotations cannot: the Two-Edit Rule that promotes a repeated edit into a permanent rule, and the unauthenticated fallback to a labeled demo on sample drafts. It still doesn't describe the response shape or what happens when no rule qualifies.

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, VIP gating front-loaded, then the operation, then the rule semantics, then the auth fallback. Every sentence carries distinct information with no restatement of the 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?

For a single-parameter, read-only tool with no output schema, the description covers purpose, the rule that governs output, and the demo fallback. The one gap is the actual structure of what comes back (list of rules? file paths?), which an agent may want since no output schema exists.

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% and the nested draft/sent fields are already documented, so baseline is 3. The description adds interpretation: the pairs are bot draft versus what the owner really sent, and an edit recurring in two or more pairs carries special weight, which tells the agent how to construct and size the input meaningfully.

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 names a specific verb and both resources ('compares what the bot drafted with what the owner really sent') and states the concrete product ('returns the Never rules to add to voice.md'). No sibling does voice-drift comparison, so an agent can route correctly from this sentence alone.

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

Usage Guidelines3/5

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

Usage is implied (run it after collecting draft/sent pairs to derive permanent Never rules), and the token precondition is stated ('Without a member token it returns a labeled demo'). However, it never says when to prefer this over siblings such as check_safety_rules or generate_skill_upgrade_patch, nor any exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources