Skip to main content
Glama
Sign In
decimalai-mcp

decimalai-mcp

Official
by decimal-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DECIMAL_API_KEYNoOptional API key. Unlocks per-org enrichment (e.g. installed_as) on the same public endpoints.
DECIMAL_API_URLNoPoint 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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, the SKILL.md body, and how to install it: its install name (the folder it installs into) and the decimalai skills add <ref> command that writes that folder. The install part is left out for a skill that is blocked or withheld, or whose safety scan is flagged and awaiting review.

Args: slug: The skill's url_slug from search results — NOT its name. A registry name may be namespaced (owner/skill), and a slash cannot survive a single URL path segment, so a namespaced name 404s here. url_slug is the slash-free identifier minted for exactly this (owner/skill -> owner-skill); for a plain un-namespaced name the two are identical. The skill's UUID id also works.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct action on the registry: fetch one skill by slug, retrieve a ranked leaderboard, and search the registry. Descriptions reinforce the boundaries (e.g. get_skill's note that slug is not the name), so an agent will not misselect among them.

Naming Consistency5/5

All three names follow a clean verb_noun pattern (get_skill, get_leaderboard, search_skills) using snake_case consistently. The convention is predictable and readable.

Tool Count4/5

Three tools is a small but coherent set for a read-only skills registry: discover (search), inspect (get), and rank (leaderboard). It is slightly thin — no category-listing or comparison tool — but each tool earns its place.

Completeness4/5

The surface covers the core discovery workflow: search, detail lookup (including install instructions), and ranked browsing. Minor gaps exist (no category enumeration, version history, or cross-skill comparison), but agents can work around them within the stated read-only scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources