Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Metis — Add Glossary Term

add_glossary_term

Define or update field-specific terms and acronyms to maintain a consistent personal glossary 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

Tool Definition Quality

A5/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: upsert semantics (keeps created_at, overwrites definition) and return type (confirmation message). This is comprehensive.

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?

The description is concise and well-structured: a clear summary followed by detailed args and returns. Each sentence adds value without redundancy.

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?

Given the tool's simplicity (2 string params) and the presence of an output schema, the description covers all needed context: upsert behavior, use case, and retrieval sibling. It is complete.

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?

The description adds meaning beyond the schema by explaining that 'term' is the unique key and 'definition' is the stored text. With 0% schema coverage, this is essential.

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?

The description clearly states it adds or updates a glossary term, specifying the action and resource. It distinguishes from the retrieval sibling 'get_glossary' by mentioning retrieval separately.

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

Usage Guidelines5/5

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

The description explains when to use it (maintaining a personal glossary for consistent definitions) and explicitly describes the upsert behavior. It also directs to 'get_glossary' for retrieval, providing clear guidance on alternatives.

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'

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