Skip to main content
Glama

Hyperresearch Answers

Search filings, economic data, patents and the web

data_and_web_search

Returns the exact passages from the best sources on a topic, read from the record itself — SEC EDGAR company filings, FDIC bank records, FEC campaign-finance and lobbying disclosures, USPTO patents and trademarks, FRED and Census economic series, ClinicalTrials.gov registrations and openFDA records, NOAA weather and climate records, scholarly databases and books, market data and posts on X, among 120+ structured public data sources, plus the live web. Use it when you need several sources to compare or build a table from (competitor lists, pricing tables, market reports), or when the answer tool found nothing. Pass the user's overall goal as objective. Calls start at 5¢; each call is charged to the user's prepaid Hyperresearch Answers balance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "data_and_web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNostandard (5¢, the default) or max (15¢: every provider, plus structured data rows and PDF tables, for hard lookups). A paywalled article the call reads may add a surcharge of 1.5 times the article's licence cost (licence price plus transaction fee), rounded up to the cent.standard
queryYesWhat to find, as a question or a precise phrase.
objectiveNoOptional: your overall task in a sentence or two (what this query is a step toward). Used where adaptive search is enabled to pick follow-up queries, ignored otherwise; never sent to a search index as typed.
max_resultsNoHow many ranked sources to return (1-100, default 10). Up to 25 at the mode price; past 25, +5¢ plus 2¢ per started 10 results.
exclude_textNoShort phrases that must not appear in the returned text.
include_textNoShort phrases to look for in the returned text. Standard search keeps a result with any of them; max search and ask need all of them.
exclude_domainsNoNever sources on these domains (or subdomains).
include_domainsNoOnly sources on these domains (and subdomains), e.g. ["sec.gov"].
max_chars_totalNoMost characters of passage text in the whole response.
end_published_dateNoOnly sources published on or before this ISO date (YYYY-MM-DD). Undated sources are left out when a date is set.
max_chars_per_resultNoMost characters of passage text per result.
start_published_dateNoOnly sources published on or after this ISO date (YYYY-MM-DD). Undated sources are left out when a date is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint and non-idempotence, but the description adds genuinely new behavioral facts: per-call pricing (5¢ standard, 15¢ max), surcharge for paywalled articles, extra charges past 25 results, and billing against a prepaid balance. It doesn't discuss result freshness, latency, or what a failed/empty response looks like.

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?

Front-loads the core purpose before the source enumeration, then usage conditions, then cost. The long '120+ sources' inventory consumes a lot of space for what it conveys, but the three-part structure is clear and each section carries useful content.

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 12-parameter, no-output-schema search tool, the description covers purpose, alternatives, cost model, and source breadth. With the schema fully documented and annotations present, an agent has enough to select and price a call 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 description coverage is 100%, so every parameter including mode pricing and include/exclude semantics is already documented. The description adds only the usage note 'pass the user's overall goal as objective', which the schema largely covers; the rest is repetition of the mode/pricing details.

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?

States a concrete verb and output ('returns exact passages from the best sources') plus a specific resource scope: named datasets (SEC EDGAR, FDIC, FEC, USPTO, FRED, etc.) plus the live web. It also distinguishes itself from the sibling answer tool by framing itself as the multi-source/comparison option and the fallback when the answer tool found nothing.

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?

Gives explicit conditions to use it: when several sources are needed to compare or build a table, or when the answer tool returned nothing. The alternative (data_and_web_answer) is referenced implicitly as 'the answer tool', though it isn't named directly and no when-not-to-use conditions are spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.