Skip to main content
Glama
taylorleese

mcp-toolz

context_get

Retrieve complete details of a specific context by its ID to access saved information across sessions.

Instructions

Get full details of a specific context by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_idYesContext ID

Implementation Reference

  • The handler implementation for the 'context_get' tool. It extracts the context_id from arguments, fetches the context from storage, returns a not found message if missing, otherwise formats the context details and returns as TextContent.
    if name == "context_get":
        context_id = arguments["context_id"]
        context = self.storage.get_context(context_id)
        if not context:
            return [TextContent(type="text", text=f"Context {context_id} not found")]
        result = self._format_context_detail(context)
        return [TextContent(type="text", text=result)]
  • The input schema defining the required 'context_id' parameter for the 'context_get' tool.
    inputSchema={
        "type": "object",
        "properties": {
            "context_id": {"type": "string", "description": "Context ID"},
        },
        "required": ["context_id"],
    },
  • The registration of the 'context_get' tool in the list_tools method, which defines its name, description, and input schema.
    Tool(
        name="context_get",
        description="Get full details of a specific context by ID",
        inputSchema={
            "type": "object",
            "properties": {
                "context_id": {"type": "string", "description": "Context ID"},
            },
            "required": ["context_id"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves details but doesn't mention whether it's read-only, if it requires authentication, rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior.

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 that directly states the tool's function without unnecessary words. It is front-loaded and appropriately sized for a simple retrieval tool, earning full marks for conciseness.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral details and usage context, making it sufficient only for straightforward scenarios.

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

Parameters3/5

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

The input schema has 100% description coverage, with the parameter 'context_id' documented as 'Context ID'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without enhancing parameter understanding.

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 verb ('Get') and resource ('full details of a specific context'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'context_list' or 'context_search' beyond specifying retrieval by ID, which slightly limits its clarity in context.

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 such as 'context_list' for listing contexts or 'context_search' for searching. It lacks explicit instructions on prerequisites or exclusions, leaving usage context unclear.

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/taylorleese/mcp-toolz'

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