Skip to main content
Glama
Ploid MCP

Ploid MCP

Official
by ploidcom

Get research status or result

get_research_status
Read-only

Retrieve the status of a pending or completed research run by run_id, including after reconnecting, so you can check progress and collect results without restarting the research.

Instructions

Retrieve a pending or completed research_person, find_people, or find_decision_makers run by run_id, including after reconnecting. Pending runs should be checked no more often than every 5 seconds. Does not start or cancel research.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_research_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesA run_id returned by a research tool, such as person-<id> or set-<id>, up to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, open world), and the description adds genuinely new behavior: a polling cadence limit and the fact that runs remain retrievable across reconnect/session boundaries. It does not describe what a completed payload contains, but that is a modest gap given the safety profile is already declared.

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?

Two sentences, front-loaded with what it returns, then polling and exclusion constraints. No redundant restatement of the title or annotations.

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, fully documented read tool this covers the essentials: what it fetches, how often, and what it will not do. The only shortfall is the absence of any indication of the pending-vs-completed response shape, which matters slightly since no output schema exists.

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%, so the pattern, length limit, and person-<id>/set-<id> examples are already documented in the schema. The description only restates 'by run_id' and adds the provenance (returned by a research tool), which is a small but real addition — baseline 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 (Retrieve) and resource (research run status/result) and explicitly scopes it to runs created by research_person, find_people, or find_decision_makers, keyed by run_id. That scope statement is what separates it from the research tools themselves and from 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 Guidelines4/5

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

Gives real usage context: check pending runs no more than every 5 seconds, and it is valid to call after reconnecting. It also states a clear when-not ('Does not start or cancel research'), implicitly routing starting/cancelling to the research and cancel_research siblings, though it never names them.

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