Skip to main content
Glama

Read a research report

get_research
Read-onlyIdempotent

Reads a research run: its status, its stage (planning, searching, reading, writing, checking or done), how many searches, pages and sources it has, and the report once the run is completed. The report is markdown with numbered citations, or JSON for a JSON Schema with the citations of each field. Each citation names the page, its title, when it was read, the passage and whether that passage supports the sentence. A call with a progress token gets progress notifications while the run works, for up to 45 seconds. Nothing is charged.

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": {
      "id": "<id>"
    },
    "name": "get_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe run's id, as the run's start gave it.

Output Schema

NameRequiredDescriptionDefault
idNo
depthNo
errorNo
inputNo
stageNo
usageNo
reportNo
statusNo
metadataNo
progressNo
created_atNo
started_atNo
completed_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "completed_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "created_at": {
      +      "type": "string"
      +    },
      +    "depth": {
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "input": {
      +      "type": "string"
      +    },
      +    "metadata": {
      +      "type": "object"
      +    },
      +    "progress": {
      +      "type": "object"
      +    },
      +    "report": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "stage": {
      +      "type": "string"
      +    },
      +    "started_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "usage": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: progress notifications when a progress token is supplied, a 45-second cap on that waiting, and the explicit 'Nothing is charged' cost statement — all of which an agent cannot derive from structured fields.

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?

Front-loaded with the core purpose and return contents, then layered detail on report format and citations. The citation-explanation sentence is somewhat long but earns its place by telling the agent what evidence accompanies each claim; nothing is redundant filler.

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 an output schema and full annotation coverage, the description is more than sufficient, covering stage semantics, report formats, citation structure, and progress behavior. The only minor gap is the absence of guidance on polling cadence or what happens if the run is still in progress when called without a token.

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?

Schema coverage is 100% and the single parameter is already documented as 'The run's id, as the run's start gave it.' The description adds no format, sourcing, or validation detail beyond that, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Reads a research run') and enumerates exactly what is returned: status, stage, search/page/source counts, and the report once complete. The stage enumeration (planning, searching, reading, writing, checking, done) makes it unmistakably distinct from siblings like list_research, start_research, or cancel_research.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the way to poll a run by id, and the progress-token note hints at waiting behavior. However, there is no explicit guidance on when to prefer this over list_research or get_input_research, nor any stated precondition such as obtaining the id from start_research.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.