Skip to main content
Glama

context

Read-only

Inspect changed paths, baseline test results, and available source files for a verification session so coding agents can diagnose regressions and plan repairs.

Instructions

Inspect changed paths, original-suite results, and available source files.

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": {
      "session": "<session>"
    },
    "name": "context"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description only enumerates what is inspected; it says nothing about whether a valid session is required, what happens if no changes exist, or how results are shaped or truncated. It adds little behavioral context beyond the annotations.

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 front-loaded sentence with no wasted wording. Its brevity is efficient but tips into under-specification, since every sentence that would have carried usage or parameter meaning is absent.

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?

For a tool with a required, entirely undocumented parameter and no output schema, the description leaves critical gaps: how to supply 'session' and what the returned inspection data looks like. The annotations cover safety but not the operational detail an agent needs to call this correctly.

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?

The sole parameter, 'session', has zero schema description coverage, and the description never mentions it or explains what identifies a session or where the agent obtains one. With 0% coverage this is the description's job, and it does not compensate.

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 specific content categories (changed paths, original-suite results, source files) and a verb, 'Inspect', so the agent learns what will be retrieved. However, the tool name 'context' is generic, and nothing distinguishes this from siblings like read, check, or compare, which plausibly surface overlapping data. Purpose is inferable but not sharply differentiated.

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 read, compare, check, or export, and no stated preconditions such as an active session or a prior run. The agent must guess the trigger conditions from the content list alone.

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