Skip to main content
Glama

Add a word to the vocabulary

pipeline_propose_term
Idempotent

Add a term to the open vocabulary when the one you need is missing. Accepted immediately and credited to you: the vocabulary is open by design and nothing about it is gatekept. Call with no arguments to read the whole vocabulary.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
termNo
glossNo
synonymsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write flag, idempotency, and openness, but the description adds genuinely non-obvious behavior: proposals are accepted immediately with no gatekeeping and are credited to the proposer. The undocumented empty-argument read mode is also a behavioral detail the schema does not convey. It stops short of describing what happens to duplicate or rejected-looking terms or what the response contains.

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, front-loaded with the action, then the behavioral payoff, then the read-only alternative. Every sentence carries information an agent could not get from the structured fields.

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

Completeness3/5

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

The description covers purpose, immediacy, attribution, and a read mode, which is decent for a mutation tool with no output schema. However, with zero schema coverage an agent is still guessing at the enum taxonomy and the gloss/synonyms format, so it is only minimally sufficient for a four-parameter write tool.

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% across four parameters, so the description bears the full explanatory burden and largely fails it. Only 'term' is implicitly covered by the word 'term'; the meaning of 'kind' (a five-value enum), 'gloss' (3–200 chars), and 'synonyms' is left entirely to infer from property names.

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 opens with a specific verb and resource ('Add a term to the open vocabulary') and adds a trigger condition ('when the one you need is missing'). It never references any sibling tool, so an agent must rely on the names alone to know this is not the search or card tools, but the core action is unambiguous.

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 gives an explicit positive trigger ('when the one you need is missing') and discloses a second usage mode ('Call with no arguments to read the whole vocabulary'), effectively telling the agent to inspect before adding. There is no explicit when-not-to-use guidance or deduplication advice, which keeps it short of a 5.

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