Skip to main content
Glama

Linkup research result (wait)

linkup-wait-research
Read-onlyIdempotent

Polls a research task until it completes or fails, returning current status and results. If wait time expires, call again with the same id to continue without recreating or re-billing.

Instructions

Wait for a research task and return it when it is completed or failed (GET /v1/research/{id} in a loop).

Polls at Linkup's recommended cadence: 2 s, doubling up to 10 s, never above 1 request per second, and reports progress to the client. If max_wait_seconds elapses first, the task is returned with its current status (pending or processing) and done=false: call this tool again with the same id. Free; the task itself was billed when created.

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-wait-research"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id from linkup-research.
max_charsNoCap on the returned JSON size.
max_wait_secondsNoHow long this call may wait before returning the current state. Call again with the same id to keep waiting; nothing is re-created or re-billed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the exact polling cadence (2 s doubling to 10 s, never above 1 request per second), progress reporting to the client, and the timeout contract (returns current status with done=false rather than failing). It also clarifies the billing semantics of repeated calls, which annotations cannot convey.

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-loads the purpose in the first clause, then layers cadence, timeout behavior, and cost in short, non-redundant sentences. No restatement of the name or title and no filler; each sentence contributes an operational fact.

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 still tells the agent what comes back (the task when completed or failed, otherwise its current status plus done=false), which is the key return-value contract. Combined with the polling and cost details, nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for max_wait_seconds: on expiry the task comes back in pending/processing state with done=false and must be re-polled, with no re-billing. That is the critical semantic an agent needs and it goes beyond the schema's parameter text.

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?

States a specific verb and resource ('Wait for a research task and return it when it is completed or failed') and even names the underlying endpoint pattern (GET /v1/research/{id} in a loop). This distinguishes it from a single-shot retrieval, though it does not explicitly name a sibling tool as the alternative for non-blocking checks.

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?

Gives clear operating guidance: call it to block on a task, and if max_wait_seconds elapses, 'call this tool again with the same id' because the task is not re-created or re-billed. It also states the cost model ('Free; the task itself was billed when created'). It stops short of explicitly saying when not to use it (e.g. for a one-shot status check).

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