DemoDesk 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 |
|---|---|
| signups_this_weekA | List the customers who signed up in the last 7 days, newest first. |
| find_customerB | Find a customer by email and show their plan, monthly payment, status and signup date. |
| revenue_summaryA | Monthly recurring revenue (MRR) from active customers, split by plan. |
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
Each tool targets a clearly distinct question: recent signups, single-customer lookup by email, and aggregate revenue by plan. There is no realistic way to confuse these three operations, and the descriptions reinforce the separation.
Only one tool follows a verb_noun pattern (find_customer), while signups_this_week and revenue_summary are noun phrases describing reports. All are snake_case and readable, but the verb convention is not applied uniformly.
Three tools is on the thin side for a customer/revenue desk, though it covers the three core read questions. It feels like a minimal dashboard slice rather than a full tool surface.
The surface is read-only and missing obvious lifecycle operations: no listing or searching all customers, no arbitrary date ranges, no create/update of customer or plan data, and no churn or payment detail. Agents hitting anything beyond the three canned queries will dead-end.