Skip to main content
Glama

add_specialist_context

Add or update a specialist context for tailored routing and search, with optional default activation.

Instructions

Add a specialist context to the user profile, or update it if it exists.

Specialist contexts tell Metis which domains the user works in so routing
and search can be tailored. This appends to specialist_contexts in
user-config.yaml (creating the file with defaults if absent); if a context
with the same name already exists, its description is updated instead of
duplicated. Related tools: toggle_context, list_contexts.

Args:
    name: Short label for the context, e.g. "Epidemiological dashboards";
        also the key used to detect and update an existing context.
    description: One or two sentences describing what this context covers.
    active_by_default: If True (default), the context is added to
        active_contexts immediately; if False, it is stored but left
        inactive (and removed from active_contexts if already present).

Returns:
    A confirmation message stating whether the context was added (and
    activated) or an existing one was updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionYes
active_by_defaultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: appends to user-config.yaml, creates file with defaults, updates existing contexts instead of duplicating, and activation behavior based on active_by_default. This provides sufficient transparency for a straightforward mutation tool.

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

Conciseness4/5

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

Well-structured with a summary line, purpose explanation, parameter details, and return value. Each part is informative, though the parameter section could be slightly more concise. Overall efficient for the amount of information conveyed.

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

Completeness4/5

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

Given the tool's simplicity (3 parameters, no nested objects, output schema present), the description covers usage, behavior, inputs, and output. It addresses the 'how' and 'why' adequately, leaving no major gaps for an AI agent to understand the tool.

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 input schema has 0% description coverage (only titles), but the description provides comprehensive parameter documentation: explains name as key for deduplication, description content, and active_by_default's effect on activation and removal. This adds significant value beyond the schema.

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 the tool adds or updates a specialist context to the user profile, explaining its purpose for tailoring routing and search. It explicitly mentions related tools (toggle_context, list_contexts), distinguishing its role in managing contexts.

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?

The description describes when to use the tool (add/update specialist context for user domains) and mentions related tools as alternatives. It could improve by explicitly stating when not to use it, but current guidance is clear and adequate.

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