Skip to main content
Glama
Sim-xia

Blind-Auditor-MCP

reset_session

Clear the current audit session to start fresh analysis, ensuring context isolation for accurate code review.

Instructions

Reset the current audit session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'reset_session' tool. It is decorated with @mcp.tool() for registration and executes the reset logic by calling session.reset() on the global session state, returning a success message.
    @mcp.tool()
    def reset_session() -> str:
    	"""Reset the current audit session."""
    	print("DEBUG: reset_session called", file=sys.stderr)
    	session.reset()
    	return "✅ Session reset successfully."
  • Supporting method in SessionState class that implements the actual session reset logic by clearing code, history, retries, and setting status to IDLE. Called by the reset_session tool handler.
    def reset(self):
        """Reset the session state."""
        self.current_code = None
        self.retry_count = 0
        self.audit_history = []
        self.status = "IDLE"
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Reset' implies a destructive or state-changing operation, but the description doesn't clarify what gets reset (e.g., data loss, session state), whether authentication is needed, or any side effects. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary elaboration. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description's minimal approach is somewhat adequate. However, as a mutation tool ('reset') with no annotations, it lacks critical behavioral context like effects or permissions, making it incomplete for safe invocation.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and the baseline for this scenario is 4, as it appropriately avoids redundant information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('reset') and target resource ('current audit session'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'submit_audit_result' or 'update_rules' which also operate on audit sessions, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'submit_draft' or 'update_rules'. There's no mention of prerequisites, timing considerations, or exclusions, leaving the agent without context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sim-xia/Blind-Audition-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server