Skip to main content
Glama

a9n9 Deep Research

by net.a9n9

Free Quick Search

a9n9_quick_search
Read-onlyIdempotent

Free first-level search, limited per day across all callers: current news coverage (100+ languages, 250K+ sources) or scholarly papers (arXiv). Returns structured results immediately with no payment. When the daily quota is exhausted, or when you need live browsing and synthesis across sources, use a9n9_research_quote for paid deep research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
domainNonews (default): global news articles. papers: arXiv preprints.
payer_addressNoOptional Tempo payer address so free usage counts toward loyalty pricing on paid research.

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / payer_address
      Added value: +{
+  "description": "Optional Tempo payer address so free usage counts toward loyalty pricing on paid research.",
+  "pattern": "^0x[a-fA-F0-9]{40}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds key behavioral context: daily quota limits, that results are returned immediately without payment, and that it covers two domains (news and papers). This goes beyond the annotations. A minor gap is not specifying the exact quota number, but the context is sufficient.

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: first defines the tool's core purpose and behavior, second directs to alternative when quota is exhausted. Each sentence earns its place – no filler, no repetition of structured fields. Very efficient.

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 tool's simplicity (3 params, no output schema) and rich annotations (readOnly, idempotent, not destructive), the description fully covers what an agent needs: purpose, domains, quota limits, and fallback tool. Return value is implied as structured results, which matches the tool's nature. No gaps.

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 67%, meaning one parameter (payer_address) lacks schema-level description. The description itself does not explain payer_address, but the schema covers query and domain well. Domain is described via description and enum. The description adds high-level context about what each domain covers (news vs papers), which helps an agent choose. Some extra detail on query length or format would improve, but not required.

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 performs a free first-level search for news (100+ languages, 250K+ sources) or scholarly papers (arXiv), and that it returns structured results immediately. This distinguishes it from sibling tools by emphasizing its free, quota-limited nature versus paid deep research.

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 tells when to use this tool (free quick search) and when to use an alternative ('when the daily quota is exhausted, or when you need live browsing and synthesis across sources, use a9n9_research_quote for paid deep research'). Names the exact sibling tool as alternative.

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 toolsInspect
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