Skip to main content
Glama

Save a voice sample

note_user_voice

Saves an exact copy of a user's message as a voice example, helping AI assistants learn and match their tone and phrasing.

Instructions

Save one of the user's own messages, copied exactly, as an example of how they talk.

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": {
      "message": "<message>"
    },
    "name": "note_user_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral constraint — the message must be copied exactly, not paraphrased — but says nothing about duplicate handling (relevant given non-idempotent) or storage limits.

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?

A single well-formed sentence with no wasted words; the key constraint ('copied exactly') sits in the middle where it reads naturally rather than being buried.

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 one-parameter write tool with an output schema, the description covers what to pass and how (verbatim). Remaining gaps are minor: what happens when the same message is saved twice, and how the stored sample is later consumed.

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 description coverage is 0% and the single parameter is documented only as a bare string titled 'Message'. The description compensates by specifying the content: one of the user's own messages, verbatim. That is meaningful semantic guidance the schema does not supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: save one of the user's own messages as a voice/style example. The phrase 'as an example of how they talk' makes the intent distinguishable from a generic memory save, but no sibling (e.g. remember, learn_about_user) is named to confirm the boundary.

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 only implied: save a message when it exemplifies the user's speech. There is no explicit when-to-use vs. when-not, and no guidance on how this differs from the other memory/learning tools in the sibling list.

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