mcp-ai-accountability
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELIABILITY_DB | No | Path to the reliability database file. For example, './reliability.db'. |
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 |
|---|---|
| start_sessionA | Start a new tracking session for an agent. Call this at the beginning of a multi-step agent run. Returns a session_id that you should pass to later tools. |
| end_sessionB | End a tracking session and get a quick summary. |
| record_interactionB | Log one tool-call result. Call this after every important tool use so reliability can be measured. |
| get_reliability_scoreA | Get the current reliability score (0-100) for an agent. Score = percentage of successful tool calls in the last N hours. |
| analyze_failuresA | Find the most common failure patterns for an agent. Returns the tools that fail most often and sample error messages. |
| recommend_improvementsC | Give concrete, actionable recommendations to improve reliability. Based on real failure data. |
| generate_audit_reportC | Generate a full audit-style report useful for investors, compliance or internal reviews. |
| check_mcp_healthA | Simple health check against another MCP server (HTTP transport). Useful for multi-agent systems that depend on other MCP servers. |
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 8 tools
Each tool targets a distinct activity: session lifecycle (start/end), logging interactions, score retrieval, failure analysis, improvement recommendations, audit reports, and external health checks. No two tools overlap in a way that would cause confusion for an agent.
All tools follow a consistent verb_noun pattern in snake_case: start_session, end_session, record_interaction, get_reliability_score, analyze_failures, recommend_improvements, generate_audit_report, check_mcp_health. The naming is predictable and uniform.
8 tools is well-scoped for an accountability/reliability tracking server. Each tool covers a distinct part of the workflow (session management, interaction logging, scoring, analysis, recommendations, reporting, health checks) without redundancy or bloat.
The core lifecycle is covered: session start/end, interaction logging, reliability scoring, failure analysis, recommendations, and audit reports. Minor gaps exist such as session history or detailed interaction listing, but the existing tools form a complete workflow for the stated purpose.