Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

find_agent_readiness

Read-only

UNDERSTANDING — the agent-readiness leaderboard across the whole catalog. Rank providers by agent readiness, and filter to those that DO satisfy (has) or do NOT satisfy (missing) specific dimensions — e.g. has="mcp_server,protected_resource_metadata" is the OAuth-capable MCP cohort, missing="agent_card" is the addressable market for a fix. Returns agent score + band alongside the Kin Score. Priced per result — $0.005 per request plus $0.0002 per record returned (less past 100), capped at $0.50 a request, under pay-as-you-go; included in Understanding and Influence. Estimate first at /api/v1/prices/estimate. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
hasNoComma-separated dimensions the provider MUST satisfy (ANDed), e.g. mcp_server,idempotency.
bandNoRestrict to one or more agent-readiness bands.
pageNoPage number, 1-based (default 1).
sortNoRanked by agent readiness, highest first.
limitNoResults per page, 1-100 (default 25).
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
missingNoComma-separated dimensions the provider must NOT satisfy (ANDed) — the gap view.
min_scoreNoMinimum agent-readiness score, 0-100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "agent_score"
-]New value: +[
+  "agent_readiness"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
  4. Added

TDQS

A4/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 is covered; the description goes further by disclosing the cost model ($0.005/request plus $0.0002/record, capped at $0.50), plan inclusion, the estimate endpoint, and what the response contains (agent score + band alongside Kin Score). That is well beyond annotation coverage, though pagination/limits behavior is left to 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?

Front-loaded with the core purpose, then filters, then return/pricing. Dense but every clause carries information; the long pricing sentence is justified by the cost-sensitive nature of a per-record-priced tool. Slightly overstuffed in a single block.

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 8 optional params, no output schema, and no required fields, the description covers purpose, filter semantics, return contents, and cost. The main gap is not pointing to agent_readiness_dimensions for the valid dimension vocabulary, which an agent needs to construct has/missing values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by interpreting the has/missing filters semantically (ANDed cohorts, 'gap view') and supplying real dimension names and example values. band, min_score, and sort get no extra explanation beyond the schema, keeping it at 4 rather than 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'the agent-readiness leaderboard across the whole catalog. Rank providers by agent readiness' plus a filter capability. This is clearly a list/search tool over providers, distinguishable in practice from the singular get_agent_readiness, though no sibling is named explicitly.

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 concrete usage patterns with worked examples: has="mcp_server,protected_resource_metadata" for the OAuth-capable MCP cohort and missing="agent_card" as the addressable market for a fix, which tells the agent when this tool is the right one. No explicit exclusions or named alternative (e.g. get_agent_readiness for a single provider) are given.

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

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources