Skip to main content
Glama

browse_apis

Find and list APIs ranked by relevance to your natural-language intent, with filters for cost, latency, pricing model, and execution mode.

Instructions

DEPRECATED in v0.1.7. Use 'discover' instead. This alias will be removed in v1.0.0. [Original behavior preserved in this version: List APIs ranked by intent.]

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.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the deprecated status and preserves original behavior as listing APIs ranked by intent, which is sufficient for a read-only tool. It does not contradict any annotations (none exist).

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?

The description is extremely concise, using only one sentence to convey the deprecation status, alternative, and core behavior. Every part is necessary and well-structured.

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?

Given the tool has 12 parameters, no output schema, and no annotations, the description is minimal. It does not explain the ranking algorithm, pagination behavior, or how filters interact. However, the schema is well-documented, and the tool is deprecated, which lowers the need for extensive documentation.

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 coverage is 100%, so baselines at 3. The description does not add any parameter-specific information beyond what the schema already provides. It does not explain how parameters affect the result or provide usage examples.

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?

The description explicitly states the tool lists APIs ranked by intent, which is a specific verb+resource. It also distinguishes itself from the sibling tool 'discover' by indicating it is deprecated, thereby clarifying its purpose and relationship.

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?

The description clearly states the tool is deprecated and provides an alternative ('Use 'discover' instead'), including a timeline for removal. This gives explicit guidance on when not to use this tool and what to use instead.

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