Skip to main content
Glama

add_glossary_term

Define or update field-specific terms and acronyms to ensure consistent definitions across sessions.

Instructions

Add a glossary term, or update its definition if it already exists.

Maintains a personal glossary of field-specific terms and acronyms so
Metis can give consistent definitions across sessions. Upserts on the
term (an existing term keeps its created_at but takes the new definition).
Retrieve entries with get_glossary.

Args:
    term: The term, acronym, or phrase to define; serves as the unique key,
        so reusing an existing term overwrites its definition.
    definition: The definition text to store for this term.

Returns:
    A confirmation message naming the term that was added or updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
definitionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, description discloses upsert semantics (created_at preserved, definition overwritten) and return value. Adequate for a simple mutating tool; could mention idempotency or side effects but sufficient.

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?

Concise, front-loaded with core purpose, efficient use of sentences, structured with Args section. No fluff.

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

Completeness5/5

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

Complete for a two-param tool with output schema: covers purpose, behavior, parameters, return, and sibling relation (get_glossary). No gaps.

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

Parameters5/5

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

Adds significant meaning beyond schema: explains term is unique key (reuse overwrites definition) and definition is the text. Schema coverage 0% so description compensates fully.

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

Purpose5/5

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

Description states specific verb 'Add or update' and resource 'glossary term', clearly distinguishing from sibling 'add' tools like add_journal_entry by focusing on glossary terms and mentioning retrieval via get_glossary.

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?

Provides context for when to use (maintain consistent definitions across sessions) and mentions alternative retrieval tool (get_glossary). Lacks explicit when-not-to-use or exclusions, but guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis_PH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server