Demo MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseC | Add a new expense entry to the database. |
| list_expensesC | List expense entries within an inclusive date range. |
| summarizeB | Summarize expenses by category within an inclusive date range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: add_expense creates new entries, list_expenses retrieves entries with filtering, and summarize provides aggregated analysis. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern (add_expense, list_expenses, summarize), with 'summarize' being a verb-only form that still fits the action-oriented naming style. The naming is predictable and readable throughout.
With 3 tools, this server is well-scoped for expense management, covering core operations: creation, retrieval, and summarization. Each tool earns its place without feeling thin or excessive for the domain.
The tools cover basic expense tracking (create, list, summarize), but there are notable gaps in lifecycle coverage, such as updating or deleting expenses. This could limit agents in handling modifications or corrections, though core workflows are supported.