Skip to main content
Glama

add_specialist_context

Add a specialist context to your profile with a name and description, and set it to active immediately if needed.

Instructions

Add a new specialist context to the user profile.

Appends to specialist_contexts in user-config.yaml. Creates the file
with defaults if it doesn't exist yet.

Args:
    name: Short label, e.g. "Epidemiological dashboards"
    description: 1-2 sentences about what this context covers.
    active_by_default: Whether to add to active_contexts immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionYes
active_by_defaultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description reveals key behaviors (appends, creates file with defaults) but omits details like what happens on duplicate names, overwrite behavior, or required permissions. With no annotations, more transparency would be beneficial.

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 concise (3 sentences + bullet list), front-loaded with the main action, and wastes no words. Could be slightly more streamlined but overall effective.

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?

The description covers the core functionality but lacks details about the output, error handling, and edge cases. Since an output schema exists (not shown), the description could be more complete if it referenced return values.

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

Parameters4/5

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

Schema description coverage is 0%, so the description fully explains each parameter: name (with example), description (1-2 sentences), active_by_default (boolean meaning). This adds significant meaning beyond the schema.

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 clearly states the tool adds a specialist context to the user profile, specifies the target file and behavior (appends, creates if missing), and lists parameters with examples. It is specific and distinguishable from sibling tools like add_glossary_term.

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?

No guidance on when to use this tool versus alternatives (e.g., other add_* tools). The description does not mention prerequisites, conditions, or use cases for adding vs updating contexts.

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