Skip to main content
Glama

POPA Recon

Read a research answer

answer
Read-onlyIdempotent

Reads the research request named by the opaque request_id that research returned. Returns pending while research runs, or the finished POPA Recon answer and its cited source links. It does not start 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": {
      "request_id": "<request_id>"
    },
    "name": "answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault
stepsYes
answerYes
statusYes
balanceNo
buy_urlNo
sourcesYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it returns a `pending` state while work is in progress rather than blocking or erroring, and the finished result includes cited source links. It does not cover what happens for an unknown or expired request_id.

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?

Three short sentences, front-loaded with the action, followed by the return states and then the negative boundary. Nothing is redundant with the title or schema.

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 a full annotation set and an output schema, the essentials are present: where the id comes from, the pending/complete return states, and what it does not do. Only edge-case behavior (invalid or expired receipts) is unaddressed, which is a minor gap.

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 description coverage is 0% and the only field carries just a title and a 43-char pattern, so the description must do the work — and it does, telling the agent the id is opaque (not to be constructed) and that it originates from a prior `research` call. No detail on format or lifetime beyond that.

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 (Reads) and resource (the research request), identifies the opaque request_id as the handle, and explicitly distinguishes itself from the sibling that creates research with "It does not start research." An agent can tell this apart from `research` without opening any schema.

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?

Implies polling semantics ("Returns pending while research runs") and the prerequisite that request_id comes from `research`, plus an explicit exclusion for starting research. It stops short of naming `research` as the call to make to obtain a request_id, so the routing is strongly implied rather than spelled out.

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.

Resources