Skip to main content
Glama

search_apis

Find APIs that match your natural language task description, with optional cost and latency constraints.

Instructions

DEPRECATED in v0.1.7. Use 'resolve' instead. This alias will be removed in v1.0.0. [Original behavior preserved in this version: Find the best API for a task using natural language.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoDEPRECATED in v0.1.9. Prefer cost_max_per_call_usdc. Maximum USDC cost per call (e.g. 0.01). Invalid values silently ignored. When both budget and cost_max_per_call_usdc are set, the stricter (smaller) value applies.
intentYesWhat you want to do in natural language (e.g. 'summarize news articles', 'get token price')
latencyNoRequired response latency tier
min_similarityNoSimilarity threshold for vector search. Default 0.5. 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 are provided, so the description carries the full burden. It discloses deprecation status and version removal, but lacks details on side effects, authorization needs, or other behavioral traits. For a search tool, more transparency about the search process and result behavior would be helpful.

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 very concise, fitting essential information (deprecation status, alternative, original behavior) into a single sentence. It is front-loaded with the most critical point: deprecation.

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?

The description is complete regarding deprecation and usage guidance, but it does not cover return format, pagination, or other search-specific behavior. Given the tool is deprecated, this might be acceptable, but for a non-deprecated tool it would be insufficient.

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%, baseline 3. The description adds value by noting deprecation of 'budget' and the interaction between 'budget' and 'cost_max_per_call_usdc', as well as constraints on 'latency_p95_max_ms' and 'cost_max_per_call_usdc'. This provides additional context beyond the schema.

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 clearly states it finds the best API for a task using natural language, with a specific verb and resource. It also immediately indicates deprecation and directs to the sibling 'resolve', distinguishing its purpose.

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 states the tool is deprecated and instructs to use 'resolve' instead, providing a clear alternative and when-not-to-use guidance.

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