Skip to main content
Glama

Search the AI-data buyer index

search_data_buyers
Read-onlyIdempotent

Frontier Desk's dated index of AI-data buyer programs, one row per program: what it buys, the per-company figures and size screens it publishes, its stated payment trigger, exclusivity, de-identification and export method, a verbatim quote from its own page, and the day that page was read. Filter by a word in the program's name or in what it buys, or narrow to the programs that publish a per-company figure. The same rows render at https://www.frontierdesk.ai/data-buyers, with .csv and .json twins.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_data_buyers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return.
queryNoWords to find in a program name or in what it buys, for example "tickets" or "Handshake".
publishes_a_rangeNotrue for only the programs that publish a per-company dollar figure; false for only those that do not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit for behavior an agent couldn't infer: rows are dated, include a verbatim quote and the day the page was read, so the data is a point-in-time snapshot rather than live. It does not discuss result volume or ordering, though the limit cap lives in the schema.

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?

One dense but front-loaded sentence covers purpose, what a row contains, and filtering options, followed by a short pointer to the rendered mirrors. The field enumeration is long but each item is load-bearing for deciding relevance; nothing is padding.

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 no output schema, the description carries the return-shape burden and does so by listing the row's contents, which is enough for an agent to judge fit. Remaining gaps are minor for a read-only, fully documented-parameter search tool: no statement of result ordering or what an empty match looks like.

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 the baseline is 3. The description usefully clarifies that the text match spans two different fields (program name or what it buys) and explains the meaning of the range screen as "publishes a per-company figure," but it never mentions limit or the false branch of publishes_a_range, so it adds only partial meaning beyond the schema.

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?

"Frontier Desk's dated index of AI-data buyer programs, one row per program" states a specific verb+resource and immediately enumerates the fields a row carries, which tells an agent this is the roster/index tool rather than a note or guide lookup. The mirror URL and row granularity make it distinguishable from siblings without opening any schema.

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 states the two usable modes of access: free-text filtering by name or by what the program buys, or narrowing via the per-company-figure screen, and points to the web/CSV/JSON twins for the same rows. What is missing is any exclusion or routing hint relative to adjacent tools (e.g. when to pull the index row versus the underlying offer detail).

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.

Resources