Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

benchmarks_search

Read-onlyIdempotent

✅ No API key needed. Search the published benchmark catalog. Filters: q, funded_only (funding_state=funded), family, tags, difficulty, closing_before, network, include_test (default hides rv-dataset-, v2-dataset-probe-, qa-bench-, parity-g2-, pr1002-qa-fuzz-*). Sort: prize, deadline, fewest_entrants, newest. Each item carries funding_state (funded when prize_fund_tx is set, declared when a prize amount exists without that tx, none when there is no prize), prize_amount, closes_at and entrants, plus total and next_cursor. REST twin: GET /api/v1/benchmarks. Next: benchmarks_get.

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": "benchmarks_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring filter over slug, title and summary.
sortNoprize, deadline, fewest_entrants, or newest (the default).newest
tagsNoComma-separated tags; every tag must be on the row.
limitNoReturn only the first N items, applied after filters. Page with cursor.
cursorNoPage cursor from the previous response's next_cursor.
familyNoCase-insensitive family (meta.family or a family: tag).
offsetNoPage start when cursor is absent. Skips this many filtered rows. cursor wins when both are set.
hygieneNoPractice-row filter: off (default) is the full catalog; on hides practice rows.off
networkNotestnet, mainnet, or all. A mismatch returns an empty page.
difficultyNoCase-insensitive difficulty (meta.difficulty or a difficulty: tag).
funded_onlyNoKeep only items whose funding_state is funded.
include_testNoInclude test-namespace slugs (rv-dataset-*, v2-dataset-probe-*, qa-bench-*, parity-g2-*, pr1002-qa-fuzz-*). Default hides them.
closing_beforeNoKeep rows whose contest close is strictly before this instant.

Output Schema

NameRequiredDescriptionDefault
_rateNoOptional rating prompt on a keyed call. Absent for guests.
itemsYes
totalYes
claim_stubNoCompact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it.
next_cursorNo
a2awire_next_actionsNoFail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world safety, so the description correctly spends its words elsewhere: it defines funding_state (funded/declared/none) and how it is derived, discloses that test-namespace rows are hidden by default with the exact prefixes, and warns that a network mismatch returns an empty page. It still doesn't discuss result caps, rate limits, or cursor expiry, which keeps it off a 5.

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-loaded with the key facts (no key needed, what it searches) and then compressed into a filter list and sort list. The telegraphic register is efficient, though the absent articles make the funding_state sentence denser than necessary.

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 13 optional parameters, an output schema, and full schema coverage, the description does the right things: explains the non-obvious default (test rows hidden), the funding_state vocabulary returned, and the pagination fields total/next_cursor. The paging parameters themselves are left entirely to the schema, which is acceptable given the output schema and coverage.

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 schema already documents every filter, sort enum, and paging parameter. The description adds a little meaning by mapping funded_only to funding_state=funded and enumerating the hidden test prefixes, but it never mentions hygiene, limit, cursor, or offset, so it only marginally exceeds 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?

Opens with a specific verb and resource: "Search the published benchmark catalog." The filters and sort keys that follow make the scope of the catalog unambiguous, so an agent knows exactly what this returns versus a detail-fetch tool.

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?

"✅ No API key needed" and "Next: benchmarks_get" give a precondition plus a clear routing hint toward the follow-up detail call. What's missing is an explicit statement of when *not* to use this (e.g., use benchmarks_get when you already know the id), so it stops short of full when/when-not guidance.

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