decimalai-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECIMAL_API_KEY | No | Optional API key. Unlocks per-org enrichment (e.g. installed_as) on the same public endpoints. | |
| DECIMAL_API_URL | No | Point at a self-hosted / local backend. | https://api.decimal.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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_skillsA | Search the public DecimalAI skills registry. Args: query: Keyword or natural-language query (hybrid keyword/semantic search). category: Optional category filter (e.g. "retrieval", "code-review"). sort: recommended (SkillScore v2, default) | lift | popular | top_rated | efficiency | rating | recent. limit: Max results (1-50). |
| get_skillA | Get one skill's full record: trust/safety-scan status, verified benchmark evidence (lift vs no-skill baseline), SkillScore, ratings, and the SKILL.md body. Args:
slug: The skill's |
| get_leaderboardA | Ranked skills leaderboard. Args: sort: skill_score | biggest_improvement | efficiency | top_rated. category: Optional category filter (uses the registry's ranked browse view — the dedicated leaderboard endpoint is uncategorized). window_days: Ranking window in days (1-3650; ignored for skill_score). limit: Max entries (1-50). |
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 3 tools
search_skills and get_leaderboard both return ranked skill lists and accept category/sort filters, so an agent could initially confuse them; however, search_skills is query-driven and get_leaderboard is browse-oriented, and get_skill is clearly a detail lookup.
All tool names use the consistent verb_noun snake_case pattern (search_skills, get_skill, get_leaderboard), with clear and predictable prefixes.
Three tools is a well-scoped size for a read-only registry client: search, detail retrieval, and leaderboard browsing. There are no redundant extras or missing essential operations.
The surface covers the full read-only discovery lifecycle: find skills via search or leaderboard, then fetch full skill records. There are no obvious dead ends for the stated registry purpose.