AgentIndex x402

Research Job

jobs

Multi-query web research, read and synthesized into one sourced JSON brief in a single call - what would otherwise cost an agent twenty calls and its whole context window. Free status polling and result retrieval. Try GET /jobs/sample.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`subject`	Yes	Subject or question to research - a company, person, product, claim or topic.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Identifier to poll for status and fetch the finished result.
`eta_seconds`	Yes	Estimated seconds until the research brief is ready.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / subject / description

Added value: +"Subject or question to research - a company, person, product, claim or topic."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "eta_seconds": {
+      "description": "Estimated seconds until the research brief is ready.",
+      "type": "integer"
+    },
+    "job_id": {
+      "description": "Identifier to poll for status and fetch the finished result.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "job_id",
+    "eta_seconds"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description usefully adds that polling and retrieval are free and that one call replaces many, but it never states whether creating the research job itself consumes credits/payment (notable given wallet_balance, can_pay, and x402_echo siblings) or how long a job takes. Adds some value over annotations but leaves the cost/auth profile opaque.

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, front-loaded sentences with no filler. The 'twenty calls and its whole context window' clause is marketing-ish but does encode the value proposition in one phrase, so it roughly earns its place.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers the async job pattern (create, poll, retrieve). What's missing is the practical detail of how to fetch results after polling (endpoint/ID semantics) and any cost signal for the research itself.

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 description coverage is 100%, so the schema already documents 'subject' fully. The description adds nothing about the field beyond what the schema says. Baseline 3 when structured data does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource: multi-query web research read and synthesized into a sourced JSON brief in one call. That clearly separates it from thin siblings like search, news, or read_web_page, though it never names them. The purpose is unambiguous even without explicit sibling routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies an async workflow (job creation, then free status polling and result retrieval) and points to GET /jobs/sample, which is a helpful onboarding hint. But it never says when to prefer this over search, summarize, or fact_check, nor what prerequisites exist before starting a job. Usage is suggested, not specified.

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

All AgentIndex x402 tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.