Bob Research Tools

bob_research

Read-only

Answers one open research question from the live web with a short written answer and source URLs, usually in 4 to 9 seconds. Use it for a synthesized answer; use bob_search for raw links or bob_factcheck to verify a claim. Works best with one specific question, e.g. 'How do facilitators settle x402 payments?'; several questions per call tend to get one blended answer. Returns {answer, sources}. Needs an x402 payment per call; if it cannot answer in time or the input is invalid, you are not charged.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	Yes	The research question to answer, 1 to 500 characters.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`answer`	Yes	Short answer synthesized from the live web.
`sources`	No	Source URLs the answer rests on.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "answer": {
+      "description": "Short answer synthesized from the live web.",
+      "type": "string"
+    },
+    "sources": {
+      "description": "Source URLs the answer rests on.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "answer"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026
- addedInput schema / properties / q / description
```
Added value: +"The research question to answer, 1 to 500 characters."
```
First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description goes beyond annotations by disclosing timing (4 to 9 seconds), payment requirements (x402 per call), no-charge conditions on failure or invalid input, and the return shape {answer, sources}. It doesn't discuss rate limits, but the added behavioral context is substantial.

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?

The description is packed but front-loaded: core function first, then routing, then usage nuance, then payment/return details. It contains several clauses and could be trimmed slightly, but every sentence contributes actionable 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?

Given the simple one-parameter schema, existing output schema, and comprehensive annotations, the description covers all remaining gaps: when to use versus siblings, performance expectations, billing behavior, and return format. An agent has everything needed to invoke it correctly.

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 single parameter is fully documented in the schema. The description adds practical semantics by explaining that one specific question works best and that multiple questions blend into one answer, which is useful but not essential beyond schema.

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?

The description states a specific verb and resource ('Answers one open research question from the live web') and clearly distinguishes this from siblings by naming bob_search for raw links and bob_factcheck for claim verification. An agent can select it correctly without opening other schemas.

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?

Explicitly says when to use this tool ('for a synthesized answer') and when to use alternatives ('use bob_search for raw links or bob_factcheck to verify a claim'). It also adds best-practice guidance on input specificity and multi-question calls, which is strong usage guidance.

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

All Bob Research Tools 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.

Resources

Need Help?