decixa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECIXA_API_KEY | No | API key — reserved for future use | |
| DECIXA_API_URL | No | Decixa API base URL | https://api.decixa.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolveA | 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. |
| discoverA | 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. |
| search_apisA | 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.] |
| browse_apisA | 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.] |
| get_api_detailA | Get full details for a specific API by its ID. Returns endpoint URL, pricing, capability, tags, agent compatibility, schema info, use cases, trust signals (trust_evidence), and provider. Prefer trust_evidence.score (with uptime_7d / p95_latency_ms / payment_req_parsed) over legacy trust_score for new clients. The top-level |
| get_indexA | Fetch the Decixa agent index — a machine-readable overview of the platform including available endpoints, total API count, and usage guidance for AI agents. Good starting point for agents new to Decixa. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The core tools (discover, resolve, get_api_detail, get_index) have distinct purposes, but the presence of deprecated aliases (browse_apis, search_apis) that mirror functionalities introduces ambiguity. The deprecation notices help, but agents may still select the wrong tool without careful reading.
Tool names mix conventions: some are single verbs ('discover', 'resolve'), some use 'get_' prefix ('get_api_detail', 'get_index'), and others follow verb_noun pattern ('browse_apis', 'search_apis'). While still readable, the inconsistency could confuse agents expecting a uniform pattern.
With 6 tools (2 deprecated), the effective count is 4 core tools, which is appropriate for API discovery and details. The scope is well-focused, and the tools are not excessive.
The set covers key operations: listing (discover), best-match selection (resolve), detailed information (get_api_detail), and platform overview (get_index). There are no obvious gaps for the stated purpose of API discovery and inspection.