Skip to main content
Glama
Sign In

Hyperresearch Answers

by ai.hyperresearch
OverviewDiscussionsAdmin

Fetch a pending answer (free)

get_answer
Read-onlyIdempotent

Fetch the answer to an ask that came back pending, by its id (ans_...). Waits up to 45 seconds; if it is still running, it says pending again and you call it again. Free: the ask is charged once, when it finishes.

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_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive), it discloses the 45-second blocking wait, the poll-again loop, and the billing model (free, charged once when the ask finishes). Latency and cost behavior are exactly what an agent cannot infer from annotations.

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?

Three short sentences, front-loaded with the action, then the wait behavior, then the cost note. Every sentence carries information; nothing redundant.

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?

No output schema exists, and the description covers the important return nuance: a pending result that must be re-polled. For a single-param, read-only tool with annotations, the only minor gap is not naming the completion payload shape.

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?

Only one parameter and schema coverage is 0%, so the description must compensate. It restates the id and its `ans_` prefix, but doesn't say where the id comes from (presumably the `ask` response) or what a malformed id does; that is largely already implied by the schema pattern.

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 (fetch) and resource (the answer to a pending ask), scoped by id. The 'came back pending' qualifier cleanly separates it from the `ask` sibling that initiates the request.

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 a clear triggering condition: use it on asks that returned pending, and call again if still running. No explicit exclusion pointing at `ask` or `search`, but the usage context is unambiguous.

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

All Hyperresearch Answers toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources