Skip to main content
Glama

set_glossary

Replaces the entire glossary with the supplied text, updating terminology used for transcript correction. Use it to overwrite existing glossary content in one operation.

Instructions

更新术语表,整段覆盖。

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose the crucial destructive trait that the existing content is wholly replaced, not merged. It says nothing about permissions, reversibility, validation failures, or what happens on empty input, so disclosure is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses with no padding, and the overwrite warning is placed immediately after the action, so it is front-loaded. It is terse to the point of under-specification, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, parameter-format-sensitive write tool with no annotations, no output schema, and zero schema description coverage, the definition leaves most of what an agent needs (input format, failure modes, confirmation of replacement) unstated.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'text' parameter, so the description must compensate. It only implies that 'text' is the entire new glossary body; the expected format (line-delimited terms, pairs, encoding) is never stated.

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?

The description names a specific verb and resource (更新术语表 / update the glossary), so the agent can tell it is a write operation on the glossary. It does not differentiate itself from the sibling 'glossary' tool or any read counterpart, which keeps it short of a 5.

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?

'整段覆盖' (whole-block overwrite) implies usage: use this when you want to replace the entire glossary rather than amend it. However, no explicit when-to-use, when-not-to-use, or alternative (such as a correction tool) is named, leaving routing to inference.

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