Skip to main content
Glama

Linkup research result (poll once)

linkup-get-research
Read-onlyIdempotent

Fetch a research task by ID to check its status and retrieve completed answers, sources, structured output, or failure reasons.

Instructions

Read one research task (GET /v1/research/{id}). Free.

status is pending, processing, completed or failed. When completed, output holds the answer and sources (sourcedAnswer) or the JSON object (structured); when failed, error holds the reason. Poll at 2 s backing off to 10 s and never faster than once per second, or use linkup-wait-research, which does that for you.

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": "linkup-get-research"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id returned by linkup-research (or a research task from linkup-tasks-create).
max_charsNoCap on the returned JSON size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only and idempotent, but the description adds what they cannot: the call is free, the four possible status values, what the payload contains per terminal state (sourcedAnswer, structured, or error), and the rate-limit cadence. These are exactly the operational facts an agent needs to poll safely.

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

Conciseness5/5

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

Front-loaded with the operation and endpoint, then cost, then the status model, then the polling rule. Three short blocks, no restated name or title, no filler.

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

Completeness5/5

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

With no output schema, the description takes on the return-shape burden and discharges it by naming what each status yields. For a two-parameter read tool, cost, status semantics, polling cadence, and the alternative path cover everything needed to call it correctly.

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 description coverage is 100%, so both the id and max_chars parameters are already documented with defaults and bounds. The description adds nothing about either parameter (no note on id provenance or truncation behavior from max_chars), so it sits at the baseline established by a fully covered schema.

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?

"Read one research task (GET /v1/research/{id})" gives a specific verb, resource, cardinality, and the underlying endpoint. The single-shot nature ("poll once") plus the name-check of linkup-wait-research lets an agent separate it from the blocking variant without opening either schema.

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

Usage Guidelines5/5

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

States the polling policy (2 s backing off to 10 s, never faster than once per second) and explicitly routes to linkup-wait-research when the caller does not want to manage that loop. That is a concrete when-to-use and when-to-delegate rule rather than an implied one.

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