Skip to main content
Glama

add_specialist_context

Add a new specialist context or update an existing one in your profile to tailor search and routing for your public health work.

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
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It details the mechanism (appends to user-config.yaml, creates file if absent, updates existing contexts by name), the effect of the active_by_default parameter, and the return value. This is comprehensive disclosure.

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?

The description is somewhat lengthy but well-structured with a clear opening, implementation details, related tools, and parameter definitions. It could be slightly more concise without losing clarity, but it remains focused and effective.

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 presence of an output schema, return values are adequately covered. The description explains the tool's effect on the user config and active contexts. It could mention error handling, but overall it is complete enough for a mutation tool with three parameters.

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?

Schema coverage is 0%, but the description adds rich meaning to all three parameters: explains name as a key for updates, description as text, and active_by_default as controlling immediate activation. This far exceeds what the schema alone provides.

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. It specifies the resource and action, and distinguishes itself from sibling tools like toggle_context and list_contexts by naming them.

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 explains when to use this tool: to inform Metis about user domains for tailored routing and search. It mentions related tools (toggle_context, list_contexts) but doesn't explicitly define when not to use it. This provides adequate but not exhaustive guidance.

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