Patchwell

research

Destructive

Research a question on the live web and get an answer in which each sentence cites the page it came from. Use it for facts you can't answer from memory or that may have changed. Returns answer (sentences with [url] citations), claims (each sentence with its url and the quote found on that page), sources, gaps (what the sources couldn't confirm) and confidence (high/medium/low). Typically 50 to 100 seconds, longer when the research model starts cold; a slow question returns {"status": "running", "job_id"} for get_job_result. Declines questions about private individuals and about anyone's personal details (where they live, contact details, family, health, finances, tracking someone) and returns a category saying why; public figures' public roles and statements are fine. Price: $0.15 per answered question; declined and unanswered questions are free.

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": {
      "question": "<question>"
    },
    "name": "research"
  }
}

Input Schema

Name	Required	Description	Default
`context`	No	Optional constraints the answer must respect, such as country, date range or audience. Leave out personal details.
`question`	Yes	The question in plain language, up to 4,000 characters. Ask about topics, markets, products, prices, companies, regulations, places, events or published research.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / context / description

Previous value: -"Optional background: who the answer is for, what you already know, or constraints such as country or date range."New value: +"Optional constraints the answer must respect, such as country, date range or audience. Leave out personal details."

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing latency (50–100s, longer on a cold start), the async escape hatch returning {"status": "running", "job_id"}, the paid-usage model ($0.15 per answered question, free if declined or unanswered), and a content policy that returns a `category` explaining refusals. The readOnlyHint=false / openWorldHint=true annotations are consistent with a web-fetching, billed operation.

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?

Front-loaded with purpose and output shape, then latency, then policy, then price — a sensible priority order for an agent deciding whether to call. Slightly dense with the long policy clause, but every sentence carries decision-relevant information.

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?

Although there is no output schema, the description enumerates the return fields (answer, claims, sources, gaps, confidence) and the alternate async response, so an agent knows exactly what comes back. Given two simple parameters and a single-shot tool, nothing material is missing.

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% and both parameters are documented in-schema (including the 4,000-character limit and example topic types), so the description needn't repeat them. It only adds adjacent meaning via the decline policy, which hints at what question content is off-limits rather than adding syntax or format detail.

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 and resource — research a question on the live web — plus the defining characteristic (every sentence cites its source page). This distinguishes it immediately from siblings like get_job_result or transcribe.

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?

Explicit when-to-use ('facts you can't answer from memory or that may have changed'), explicit when-not (declines questions about private individuals and personal details), and names the follow-up tool (get_job_result) for slow jobs. Nothing is left to inference about routing.

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

All Patchwell tools Inspect

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.