Skip to main content
Glama

glossary_terms_add

Add terms in bulk; the answer is counts.

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": {
      "glossary_id": "<glossary_id>",
      "terms": "<terms>"
    },
    "name": "glossary_terms_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
termsYes
glossary_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and mostly fails. It discloses only that the operation is bulk and that the response is "counts," without saying what counts (added vs. skipped vs. failed), whether duplicates overwrite or error, what the 2000-item cap implies, or what permissions are required for a mutation.

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

Conciseness3/5

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

Two short clauses with no filler and the action front-loaded, which is good, but the second clause ("the answer is counts") is ambiguous and the extreme terseness leaves the actual behavior unexplained rather than crisply summarized.

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?

This is a bulk mutation over a nested term structure with no annotations and no output schema, so the description should explain merge semantics, limits, and the failure/count breakdown. Instead it gives a single sentence fragment that leaves an agent guessing on nearly every operational question.

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% and both parameters are required, yet the description says nothing about glossary_id being the target glossary or about the term object's fields (source_term, target_term, variants, do_not_translate, forbidden_targets). The phrase "terms in bulk" only gestures at the array parameter.

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

Purpose3/5

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

"Add terms in bulk" names a verb and a resource, so the core purpose lands, but it never says these are glossary terms tied to a glossary_id, nor distinguishes the tool from siblings like glossary_create or glossary_get. The trailing fragment "the answer is counts" is too vague to sharpen the purpose.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites such as an existing glossary_id, and no indication of what happens versus glossary_create. The agent must infer that a glossary must already exist and that this is the bulk path.

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