Skip to main content
Glama

discover

List APIs ranked by intent for AI agents to select from. Filter by budget, latency, and more to find the right API.

Instructions

List APIs ranked by intent. Returns multiple candidates so the agent can choose. Decixa uses Phase 3 vector + scoring to rank verified-x402 APIs. Use this when you want to see options — use resolve when you want a single recommendation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by capability tag (e.g. 'Market Data', 'Risk Score').
sortNoSort preset. 'relevance' uses Phase 3 normalized score. 'calls' is deprecated and will be removed in Phase 4. Default: relevance.
limitNoNumber of results per page. Default: 20
budgetNoDEPRECATED in v0.1.9. Prefer cost_max_per_call_usdc. Maximum USDC cost per call. Invalid values silently ignored. When both budget and cost_max_per_call_usdc are set, the stricter (smaller) value applies.
intentYesNatural-language intent. Mapped to the server's 'task' query parameter.
offsetNoPagination offset. Default: 0
latency_tierNoFilter by latency tier
pricing_modelNoFilter by pricing model
execution_modeNoFilter by execution mode
min_similarityNoSimilarity threshold for vector search. Default 0.3. Out-of-range returns 400.
latency_p95_max_msNov0.1.9 (D-084): Maximum measured p95 latency in milliseconds. Invalid values (≤0, NaN) return 400. APIs with no measured p95_latency_ms are excluded from results when this filter is set.
cost_max_per_call_usdcNov0.1.9 (D-084): Maximum cost per call in USDC. Invalid values (negative, NaN) return 400. When both budget and this are set, the stricter (smaller) value applies.
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions 'returns multiple candidates' and ranking mechanism, but lacks details on rate limits, auth needs, or failure behavior. Adequate for a read-like tool but could be more transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (two sentences plus a comparison), front-loaded with the purpose, and every sentence is informative.

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

Completeness2/5

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

Given 12 parameters and no output schema, the description only says 'returns multiple candidates' without explaining structure, pagination, or how to use results. Incomplete for rich decision-making.

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 has 100% description coverage for all 12 parameters, so baseline is 3. Description adds no extra context beyond the schema for any parameter.

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?

Description clearly states 'List APIs ranked by intent' with specific verb and resource. Explicitly differentiates from sibling tool 'resolve' by stating when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool ('when you want to see options') and when to use the alternative ('use resolve when you want a single recommendation'). Provides clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/koki-socialgist/decixa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server