Skip to main content
Glama

Defined term set metadata

bpj_glossary_defined_terms
Read-onlyIdempotent

Build a DefinedTermSet with term names and definitions from pipe-separated rows.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
termsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds only the input-assembly detail and says nothing about whether input is validated, what happens on malformed rows, or that the result is a composed metadata blob rather than a stored resource.

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 sentence with the verb and resource front-loaded and zero redundant wording. Nothing could be removed without losing information.

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?

With two required parameters, no output schema, and no example of what a DefinedTermSet result looks like, the description leaves the agent guessing about the return shape and the exact row format. It is minimally adequate for calling the tool but not complete.

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 description coverage is 0%, so the description must carry the weight and it partially does by explaining that `terms` holds pipe-separated term/definition rows. However, it leaves the relationship between pipe separators and line breaks ambiguous against the schema title 'Term|definition, one per line', and says nothing about the `name` parameter.

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 ('Build a DefinedTermSet') and states the input shape it consumes ('term names and definitions from pipe-separated rows'). It does not reference any sibling tool, but the sibling list is a broad catalog of unrelated metadata utilities, so differentiation is not the main gap here.

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 framing, no exclusions, and no prerequisites; the agent must infer that this tool produces structured glossary metadata rather than performing a lookup. Only the input-format clause hints at the intended scenario.

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.