Agent Service Directory

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'.
`scope`	No	directory (default): services that meet the listing criteria (https://agentservicedirectory.com/methodology#directory); index: everything we watch.
`branch`	No	Capability tree id from get_tree, e.g. 'places/weather' or 'places' (a branch includes its leaves), or 'other'.
`offset`	No
`network`	No	Payment network, e.g. 'eip155:8453' (Base) or 'solana'.
`passing`	No	true: latest check passed.
`provider`	No	Only endpoints from this provider (registrable domain, e.g. 'example.com'), as given in a result's provider field.
`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 (registrable domain): 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.

Changed4 schema fields changedOct 17, 2026

addedInput schema / properties / branch

Added value: +{
+  "description": "Capability tree id from get_tree, e.g. 'places/weather' or 'places' (a branch includes its leaves), or 'other'.",
+  "maxLength": 80,
+  "type": "string"
+}

changedInput schema / properties / one_per_provider / description

Previous 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)."New value: +"Return one endpoint per provider (registrable domain): the first under the chosen sort (by default, the most scheduled checks passed in the 30-day window)."

addedInput schema / properties / provider

Added value: +{
+  "description": "Only endpoints from this provider (registrable domain, e.g. 'example.com'), as given in a result's provider field.",
+  "maxLength": 253,
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "description": "directory (default): services that meet the listing criteria (https://agentservicedirectory.com/methodology#directory); index: everything we watch.",
+  "enum": [
+    "directory",
+    "index"
+  ],
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that — result compactness and limit/offset paging — but says nothing about authorization, rate limits, or how evidence is surfaced in results.

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?

Four short sentences with the purpose front-loaded and no filler. It is efficient, though the paging note is tacked on the end rather than integrated into the filter-then-fetch flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter, zero-required discovery tool with no output schema, the description covers the search-then-get_service workflow but gives only a thin sketch of what results contain ('compact') besides evidence. Adequate, but an agent still has to infer result shape and filter interactions.

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 78%, and the schema itself documents the notable params (scope, branch, min_payers, max_terms_changes_90d). The description only names passing/min_pass_rate/max_price_usd and limit/offset, mostly repeating schema content rather than adding syntax or interaction semantics, so baseline 3 applies.

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') plus scope ('by purpose, with evidence for each'). It also implicitly separates itself from get_service by deferring connection details to that sibling, so an agent can tell the two apart.

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 evidence fields, pick one result, then call get_service for connection details, and use limit/offset for paging. It does not state when NOT to search or mention other sibling discovery tools (get_tree, get_changes), but the primary routing decision is explicit.

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

All Agent Service Directory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?