Skip to main content
Glama

get_context

Read pinned requirements, decisions, documents, and review history by run ID with a stable context hash for bounded, repeatable context retrieval.

Instructions

Read pinned requirements, decisions, documents and review history with a stable context hash.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the useful trait of a 'stable context hash,' but says nothing about permissions, whether reads are side-effect free, pagination behavior, or what happens when limit/offset are used.

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?

It is a single front-loaded sentence with no wasted wording. Brevity is appropriate, though the space saved is not used to add needed parameter or usage detail.

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?

With no annotations, no output schema, and zero schema description coverage across three parameters, the definition is under-specified for an agent to invoke it confidently. It omits pagination semantics, return shape, and how the stable hash should be interpreted.

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

Parameters1/5

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

Schema description coverage is 0%, with three parameters (run_id, limit, offset) documented only by titles and defaults. The description explains none of them, including the meaning of the stable context hash relative to run_id or how limit and offset paginate results.

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 uses a specific verb ('Read') and enumerates the resource types returned: pinned requirements, decisions, documents, and review history. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as get_artifacts or get_run.

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 guidance on when to use this tool versus alternatives like get_artifacts, get_diff, or get_run, and no stated preconditions. The only implied usage is reading pinned context, which an agent must infer.

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