Skip to main content
Glama

vocabulary

Read-onlyIdempotent

The CLEAR vocabulary the Gate checks against: approved verbs with their signatures (the arguments each takes), question patterns, glossary, units, connectors. Not every approved verb is a citizen's: commands lists what the world runs for you; the operator's verbs and the invitation's out-of-world ones are approved so the checker can read a message that uses them. Long; section returns one part. No name needed.

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": "vocabulary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoOne section alone: approved_verbs (with signatures), ask_patterns, glossary, units, connectors, or another top-level key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section
      Added value: +{
      +  "description": "One section alone: approved_verbs (with signatures), ask_patterns, glossary, units, connectors, or another top-level key.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/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 description's added value is what the response contains and how big it is. Saying the result is long and that `section` returns a single part is a real operational caveat an agent needs before calling. It also warns that some approved verbs in the output are not callable by the citizen, which prevents misreading the result.

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?

The scope-defining sentence comes first and the payload-size caveat with the `section` escape hatch follows logically. The middle sentence about operator and out-of-world verbs is dense and jargon-heavy but does earn its place by explaining why the list is longer than the citizen's own verbs.

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?

There is no output schema, so the description must explain the return shape, and it does by enumerating the categories of content returned. With one optional parameter fully documented and rich annotations, the agent has what it needs to call this correctly; only the naming of 'another top-level key' is left vague.

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

Parameters3/5

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

Schema coverage is 100% and the `section` enum-ish values are already described in the schema, so the schema carries most of the weight. The description only adds the rationale ('Long; `section` returns one part') and notes no name is required, which is marginal beyond the schema. Baseline 3 applies.

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 the specific resource (the CLEAR vocabulary the Gate checks against) and enumerates its contents: approved verbs with signatures, question patterns, glossary, units, connectors. It also distinguishes itself from the sibling `commands`, which lists what the world runs for you. Jargon like 'CLEAR' and 'citizen's' keeps it from being fully self-explanatory, but the verb+resource are clear.

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?

It tells the agent to use `commands` instead when it wants what the world runs on its behalf, and directs it to the `section` parameter when it only wants one part because the full payload is long. It gives no explicit guidance about when to consult this versus `schema`, `check`, or `gate`, so it falls short of a complete when/when-not map.

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.