session_close
One-call session close. Runs drift_audit scope=full, then all 3 propagators. Returns combined results. The end-of-session button.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Nervous System
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds context beyond annotations by detailing the internal steps (drift_audit, propagators) and combined results, though annotations declare destructiveHint=false and propagators may imply modifications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no fluff, front-loaded with the core function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Provides key steps and return value mention, but lacks output format details and prerequisites (e.g., session must exist).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; schema coverage is 100%, so no additional parameter information is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool closes a session by running drift_audit and all 3 propagators, distinguishing it from siblings like drift_audit and propagate_family_member.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use at session end with 'The end-of-session button', but does not explicitly exclude alternatives or specify prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but there is some overlap among multiple audit/check tools (e.g., accountability_check, drift_audit, security_audit). However, descriptions and naming help differentiate their specific scopes, so ambiguity is low.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_archive_safety, propagate_family_member), making them predictable and easy to understand.
Tool Count4/5
33 tools is on the high side, but the server covers a broad domain (system health, audits, propagation, session management, etc.). The count is justified by the comprehensive scope, though it may feel heavy for agents.
Completeness5/5
The tool set covers the entire lifecycle of system management: health monitoring, audits, propagation, sessions, compliance, and more. No obvious gaps for the stated purpose of a nervous system framework.