Skip to main content
Glama

resolve

Find an API for a task described in natural language. Provides the top recommendation and up to two alternatives, with budget and latency filtering.

Instructions

Find the best API for a task using natural language. Returns the top recommendation and up to 2 alternatives. Decixa uses Phase 3 vector + scoring to rank verified-x402 APIs by intent. When no candidate clears the similarity threshold, returns recommendation_status='no_match' with suggestions. Use this when you want Decixa to pick — use discover when you want to see the list.

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

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

No annotations provided, but description covers key behaviors: vector scoring, threshold, no_match return with suggestions. Transparent about recommendation logic without need for annotations.

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?

Three sentences, front-loaded with core purpose and result. No unnecessary words. Efficient and clear structure.

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?

Covers recommendation logic, fallback behavior, and distinguishes from sibling tool. No output schema, but description explains return values. Could slightly improve by noting required parameter or error cases, but overall complete.

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 100%, baseline 3. Description adds minimal parameter-level context (only mentions 'intent' implicitly). Schema already defines all parameters with descriptions.

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 using natural language, returns top recommendation and alternatives. It distinguishes from sibling tool 'discover' by specifying 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 says 'Use this when you want Decixa to pick — use discover when you want to see the list', providing clear when-to-use and when-not-to guidance with named alternative.

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