careops-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsA | List clients, optionally filtered by suburb or preferred language. Use this to find a client before scheduling a visit or answering questions about the client base. |
| get_clientB | Get one client's full record, including their upcoming visits. |
| schedule_visitA | Schedule a care visit. Input is strictly validated (Pydantic). Rejects past dates, malformed times, and out-of-range durations before anything touches the database. Refuses to double-book a carer at an already-scheduled date and start time. |
| check_complianceA | Report carer certifications that are expired or expiring soon. Aged-care providers must not roster carers with lapsed mandatory certifications (First Aid, Police Check). Use this before assigning visits or for a weekly compliance review. |
| verify_audit_logA | Verify the integrity of the hash-chained audit log. Re-computes every entry's SHA-256 link. Returns valid=false with the breaking line number if any record was altered or removed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| audit_log | The full audit trail of tool calls, one JSON entry per line. |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: compliance checking, client retrieval, client listing, scheduling, and audit verification. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (check_compliance, get_client, list_clients, schedule_visit, verify_audit_log). No mixing of conventions.
With 5 tools covering compliance, client management, scheduling, and audit, the count is well-scoped for the care operations domain. Each tool adds clear value.
The tool set covers key workflows: compliance checks, client lookup, visit scheduling, and integrity verification. Minor gaps exist (e.g., no tool to update or cancel a visit), but the core lifecycle is supported.