Cerell-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infraC | Cerell infra gateway: compare/provision/connect partners, status/optimize/evolve stack, cashback/portal. Compact JSON; add detail=1 or limit=N in request for more. |
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 1 tool
With only one tool, there is no cross-tool overlap or misselection risk. However, the single tool bundles many distinct operations (partners, stack, cashback, portal), so agents must disambiguate through parameters rather than tool choice.
There is only one tool name, so consistency cannot be meaningfully evaluated. The name 'infra' is broad and does not follow a verb_noun pattern, but it is readable.
The apparent scope spans partner provisioning, stack optimization, evolution, cashback, and portal operations. Collapsing all of that into one mega-tool is too thin for the domain and forces excessive reliance on parameter conventions.
The description mentions several major capability areas, suggesting broad coverage, but the surface lacks granular operations and clear CRUD/lifecycle boundaries. Agents may work around this with the detail/limit parameters, but specific workflows are opaque.