mcp-server-and-agent
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recordsA | Search the record store by a free-text query matched against title, owner and tags. Returns matching record ids. |
| fetch_recordA | Fetch one record by its exact id. Returns the record's title, owner, amount and tags. |
| summarise_amountsA | Compute count, total and mean of the amount field across the given record ids. All ids must exist. |
| append_noteB | Append a free-text note to the session note log. |
| delete_recordA | Permanently delete a record. Destructive and gated: the first call returns a confirm_token describing what would be deleted, and the deletion only happens on a second call carrying that token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_owner | Draft the tool plan for auditing every record belonging to one owner. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Record store schema | Field names, types and valid enum values for the record store. |
TDQS
Scored across 5 tools
Each tool performs a distinct action: searching, fetching by ID, aggregating amounts, appending notes, and deleting records. There is no overlap or ambiguity between them.
All tool names consistently follow the verb_noun pattern (search_records, fetch_record, summarise_amounts, append_note, delete_record), using uniform snake_case naming.
With 5 tools, the surface is well-scoped and covers essential operations without bloat or unnecessary duplication. The count is appropriate for a focused record management server.
The tools cover search, fetch, aggregation, note appending, and deletion, but lack create and update operations. While the server may be intentionally read-only plus deletion, the asymmetry is a notable gap for a record management domain.