a9n9 Deep Research

Quote Deep Research

a9n9_research_quote

Read-onlyIdempotent

Analyze a deep-research objective and return the exact current price, limits, planned start URLs, request hash, expiry, payment requirements, and cloud-browser capabilities without charging or starting a job. targetUrl is optional: omit it and the quote derives and binds a bounded plan of public start URLs from the objective.

Input Schema

TableJSON Schema

Name	Required	Description
`job_key`	Yes	job_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical request retries idempotently. Sessions are referenceable for 7 days, then results are cleared.
`objective`	Yes
`targetUrl`	No	Optional public HTTPS focus hint; when omitted the service plans up to 5 public start URLs from the objective and binds them into the quote.
`payer_address`	No	Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	Yes
`price`	Yes
`limits`	Yes
`chainId`	Yes
`network`	Yes
`payment`	Yes
`quoteId`	Yes
`currency`	Yes
`nextStep`	Yes
`expiresAt`	Yes
`rationale`	No
`cloudBrowser`	Yes
`walletPayment`	Yes
`requestBodyHash`	Yes
`paymentChallenge`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / job_key / description

Previous value: -"Caller-generated unique key for one intended job; reuse only for retries."New value: +"job_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical request retries idempotently. Sessions are referenceable for 7 days, then results are cleared."

Changed1 schema field changedAug 18, 2026

addedInput schema / properties / payer_address

Added value: +{
+  "description": "Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.",
+  "pattern": "^0x[a-fA-F0-9]{40}$",
+  "type": "string"
+}

First observedAug 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral nuance: it binds a bounded plan of start URLs when targetUrl is omitted, and clarifies that the quote does not trigger payment or job start. This complements the annotations without contradicting them.

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?

The description is two sentences, front-loaded with the core purpose and immediately followed by the key optionality. Every sentence carries critical information with no filler.

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?

For a fairly complex quote tool with an output schema (present but not shown), the description covers the essential behavior, optional parameters, and outcomes without redundancy. It does not need to describe return values since the output schema exists, and the description is sufficiently complete in context.

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 covers 75% of parameters with descriptions. The tool description adds meaning beyond the schema: it explains the optionality of targetUrl and its effect (planning up to 5 start URLs) and hints at job_key reuse for follow-ups. Since schema coverage is high, the baseline is 3, but the description's added nuance earns a 4.

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 clearly states the tool's purpose: 'Analyze a deep-research objective and return the exact current price, limits, planned start URLs, request hash, expiry, payment requirements, and cloud-browser capabilities without charging or starting a job.' This distinguishes it from siblings like a9n9_research_start (which starts a job) and a9n9_quick_search (a different search type).

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?

The description implies when to use this tool: before starting a job, as it explicitly says 'without charging or starting a job.' It also explains the optional targetUrl behavior, giving context on how to influence planning. However, it does not explicitly name alternatives or state 'do not use when...' which prevents a 5.

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

All a9n9 Deep Research tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a distinct role: quick_search is the free tier, while research_quote, research_start, research_status, and research_submit_payment form a clear paid workflow. No two tools could be plausibly confused.

Naming Consistency4/5

All tools share the a9n9_ prefix and snake_case convention. Minor inconsistency exists because quick_search breaks the research_* pattern used by the other four tools, but the verb/noun usage is otherwise predictable.

Tool Count5/5

Five tools is well-scoped for a research service: one free entry point and four lifecycle steps (quote, start, payment, status). Each tool serves a necessary and non-redundant function.

Completeness4/5

The core deep-research workflow is fully covered: free quick search, quote, paid start, payment submission, and status/result retrieval. Minor gaps like cancellation or job listing are absent but not essential to the primary purpose.

Resources

Need Help?