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 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond annotations: no charge is incurred, no job is started, and omitting targetUrl causes the service to derive and bind a bounded plan of public start URLs from the objective.

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?

Two sentences with front-loaded purpose and no filler. Each clause contributes either output details, side-effect guarantees, or targetUrl behavior, making the description efficient and well-structured.

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 rich schema, annotations, output schema, and sibling tool names, the description is complete: it enumerates the quote's returned fields, clarifies the optional targetUrl behavior, and leaves no major ambiguity about the tool's role.

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 description coverage is 75% and the schema already details job_key, targetUrl, and payer_address. The description adds value by explaining that targetUrl is optional and that omitting it triggers plan derivation/binding, which enriches the schema's format-only definition.

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 uses a specific verb and resource ('Analyze a deep-research objective and return...') and lists concrete outputs: price, limits, planned start URLs, request hash, expiry, payment requirements, cloud-browser capabilities. It also distinguishes itself from siblings with 'without charging or starting a job.'

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?

It clearly establishes the quoting/planning use case and explains what happens when targetUrl is omitted. It does not explicitly name sibling alternatives or state when not to use it, but the 'without charging or starting a job' phrasing implies pre-flight use before research_start.

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 serves a distinct purpose: free search, quote generation, paid research initiation, status tracking, and payment submission. No two tools overlap in functionality, and descriptions clearly differentiate their roles.

Naming Consistency4/5

All tools share the 'a9n9_' prefix and use snake_case. However, the pattern varies slightly: 'quick_search' uses adjective_noun, while others mix noun_noun and verb_noun constructions. The inconsistency is minor and does not hinder readability.

Tool Count5/5

Five tools cover the essential stages of the research service (free search, quoting, payment, start, status) without unnecessary redundancy. The count is well-scoped for the domain.

Completeness4/5

The tool set covers the main workflow end-to-end. A minor gap is the lack of a tool to list or cancel past research jobs, but the core lifecycle (quote, pay, start, status) is fully represented.

Resources

Need Help?