Skip to main content
Glama

get_context

Retrieves a small, budgeted bundle of task-relevant memory for AI coding agents, helping them start tasks with scoped knowledge instead of replaying history.

Instructions

Return a small, budgeted task-relevant memory bundle.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
scopeNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It hints at two traits — output is size-limited ('small, budgeted') and filtered by relevance ('task-relevant') — but never says how relevance is computed, whether the result is empty-safe, how the scope narrows results, or what happens with the default empty task. That is thin for a no-annotation tool.

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

Conciseness3/5

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

A single sentence with no filler, so it is concise. However, conciseness here comes from under-specification rather than editing — the sentence is front-loaded but too compressed to convey the tool's contract.

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

Completeness2/5

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

An output schema exists, so return-value detail is not required. But the scope parameter is a seven-dimension object with conservative matching semantics that materially changes retrieval behavior, and the description never mentions it, nor does it mention the actor handle. For a memory-retrieval tool with a complex scope argument and no annotations, this leaves major gaps.

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

Parameters2/5

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

Schema description coverage is 0% and the three parameters (task, scope, actor_handle) are undocumented at the top level. The description's phrase 'task-relevant' only loosely gestures at the task parameter and says nothing about scope or actor_handle, leaving two of three parameters unexplained in both schema and description. The rich Scope $defs prose lives in the schema, not the description, so it does not compensate here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Return') and an object ('task-relevant memory bundle'), so the general intent is retrievable. But 'budgeted' and 'bundle' are unelaborated jargon, and nothing distinguishes this from retrieval siblings such as search or get_entry, so an agent cannot tell which retrieval tool to pick from this line alone.

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?

There is no statement of when this tool should be used, when it should not, or what alternative to prefer. With zero guidance, an agent facing several retrieval-ish siblings has to guess based on the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.