Agent Service Atlas

Search services

search_services

Read-only

Find payable APIs and agent task marketplaces by purpose, with evidence for each. Filter on the evidence (passing, min_pass_rate, max_price_usd) and pick one; then call get_service for connection details. Results are compact; use limit/offset to page.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Purpose tag, e.g. 'web-search'.
`sort`	No
`tier`	No
`type`	No
`limit`	No	Default 10, maximum 25.
`query`	No	Free text matched against name, host, URL and operator, e.g. 'weather' or 'translate'.
`offset`	No
`network`	No	Payment network, e.g. 'eip155:8453' (Base) or 'solana'.
`passing`	No	true: latest check passed.
`min_checks`	No	Minimum checks in the last 30 days, to avoid judging on one check.
`min_payers`	No	Minimum unique payers in 30 days, as reported by the registry.
`max_price_usd`	No	Maximum price per call in USD stablecoin, where the price is known.
`min_pass_rate`	No	Share of checks passed in the last 30 days, 0 to 1.
`one_per_provider`	No	Return one endpoint per provider host: the first under the chosen sort (by default, the most scheduled checks passed in the 30-day window).
`max_terms_changes_90d`	No	Only services whose observed x402 payment terms changed at most this many times in the last 90 days (0 = unchanged). Short histories are labelled limited.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / max_terms_changes_90d

Added value: +{
+  "description": "Only services whose observed x402 payment terms changed at most this many times in the last 90 days (0 = unchanged). Short histories are labelled limited.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / one_per_provider / description

Previous value: -"Return only the best endpoint from each provider."New value: +"Return one endpoint per provider host: the first under the chosen sort (by default, the most scheduled checks passed in the 30-day window)."

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and boundedness are covered. The description adds genuinely useful context beyond that: results carry evidence per service, they are compact, and pagination is via limit/offset. It does not describe the full result shape, but no contradiction with annotations exists.

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?

Three sentences, front-loaded with purpose, then workflow, then paging. Each sentence earns its place, though the parenthetical filter list is slightly dense and the paging note could be merged.

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?

For a 15-parameter search tool with no required args and no output schema, the description covers purpose, the key evidence filters, the downstream step, and paging. It stops short of characterizing the returned record structure, but the workflow an agent needs to call it correctly is present.

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 73%, so the schema already documents most parameters, including the three filters the description names (passing, min_pass_rate, max_price_usd). The description adds only a framing hint ('filter on the evidence') and no syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 specific verb and resource: 'Find payable APIs and agent task marketplaces by purpose, with evidence for each.' It also scopes the result set and points to the sibling (get_service) that consumes this tool's output, so an agent can place it in the family without opening a 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?

Gives a clear workflow: filter on the evidence fields, pick one, then call get_service for connection details. It tells the agent how this tool fits before and after, but offers no explicit when-not-to-use guidance or alternatives for narrowing a search (e.g. tag vs query).

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

All Agent Service Atlas tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?