Skip to main content
Glama

list_available_contexts

View all loaded context categories and their descriptions to understand available persistent tool settings across chat sessions.

Instructions

List all loaded context categories and their descriptions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list_available_contexts' tool handler retrieves context information from the engine, transforms it into a summary (including tool_category, description, priority, and applies_to), and returns it as a JSON-formatted string.
    case 'list_available_contexts': {
      const contexts = engine.getContexts();
      const list = Array.from(contexts.values()).map((c) => ({
        tool_category: c.tool_category,
        description: c.description,
        priority: c.metadata.priority ?? 'medium',
        applies_to: c.metadata.applies_to_tools,
      }));
      return { content: [{ type: 'text', text: JSON.stringify(list, null, 2) }] };
    }
  • The tool 'list_available_contexts' is defined and registered in the MCP server's listTools response.
    {
      name: 'list_available_contexts',
      description: 'List all loaded context categories and their descriptions',
      inputSchema: {
        type: 'object' as const,
        properties: {},
      },
    },
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It adds the qualifier 'loaded,' implying a runtime state distinction from all possible contexts, but fails to disclose whether this operation is expensive, cached, or what format the returned categories and descriptions take.

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 a single, efficient sentence of seven words with the action verb front-loaded. There is no redundant or wasted text, and the brevity matches the simplicity of the parameterless operation.

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?

For a zero-parameter discovery tool without output schema, the description adequately identifies what it returns (categories and descriptions). However, given the lack of annotations, it could enhance completeness by clarifying what constitutes a 'context category' in this system or hinting at the return structure.

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?

The tool accepts zero parameters, establishing a baseline score of 4. The description appropriately indicates no inputs are required by omitting parameter references entirely, consistent with the empty input 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 provides a specific verb (List) and resource (context categories), clearly indicating it retrieves available context metadata. It implicitly distinguishes from sibling get_tool_context (which likely retrieves specific tool context) by emphasizing it returns 'all loaded' categories and their descriptions, though it could explicitly contrast with the singular retrieval tool.

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?

The description provides no guidance on when to use this tool versus alternatives like get_tool_context, nor does it indicate prerequisites or typical workflow positioning (e.g., whether this should be called before other context-related operations).

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/doobidoo/MCP-Context-Provider'

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