Skip to main content
Glama

research_context

Read-onlyIdempotent

Read stage guidance, local memories, and confirmed conditions before choosing resources, editing scripts, preparing runs, or recovering; asks only unresolved choices and saves discussion pauses.

Instructions

Read stage guidance, local memories and confirmed conditions before choosing resources, editing scripts, preparing runs or recovering. Ask only unresolved scientific choices. Save pause before further actions when the user asks to discuss.

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": {
      "task_id": "<task_id>"
    },
    "name": "research_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds procedural guidance ('Ask only unresolved scientific choices', 'Save pause before further actions when the user asks to discuss'), which is genuinely extra context, but the phrasing is opaque and says nothing about what context is returned or how the task scope constrains it. Output schema exists, so return-format gaps are forgivable.

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?

Short and front-loaded with the read purpose, but the follow-on sentences are fragmented and 'Save pause before further actions' is grammatically unclear, forcing the reader to decode intent. Instruction-like fragments are mixed into what should be a definition.

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

Completeness4/5

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

For a single-parameter read tool with full annotation coverage and an output schema, the definition supplies enough to call it correctly and know when to reach for it. The remaining gaps are the undefined domain terms and the missing explanation of how task_id bounds the returned context.

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?

There is a single required parameter, task_id, with 0% schema description coverage, and the description never mentions it. An agent must infer that task_id scopes which stage guidance and memories are read. With low coverage, the description should have compensated and does not.

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 verb is 'Read' and the resource list is 'stage guidance, local memories and confirmed conditions', so the general shape of the operation is discernible. However, terms like 'stage guidance' and 'confirmed conditions' are undefined domain jargon, and 'local memories' overlaps with the sibling tool memory_get without any differentiation. The rest of the text drifts into agent-behavior instructions rather than clarifying what the tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete triggering moments: before choosing resources, editing scripts, preparing runs, or recovering, plus a separate trigger for when the user asks to discuss. What's missing is any when-not condition or pointers to adjacent tools (e.g., memory_get) for narrower lookups.

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