Clear session transcripts or delete entire sessions to reset collaborative review environments.
Clear a session transcript or delete the session entirely
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | ||
| idempotency_key | Yes | Stable key for this operation (e.g. review-auth-jwt-1). Reuse the same key when retrying after timeout. | |
| expected_version | No | ||
| keep_metadata | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Destructive operation is implied but no details on irreversibility, auth requirements, or what exactly gets cleared/deleted. No annotations to supplement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Too short and vague to convey essential context. Single sentence fails to explain tool behavior sufficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Missing output schema, no annotations, 4 parameters mostly undocumented; description incomplete for safe effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 25% (only idempotency_key described). Description adds no parameter meaning; does not compensate for missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states it clears or deletes a session, but doesn't specify which condition triggers which action. It distinguishes from siblings as reset/delete operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus other peer tools, no context about prerequisites or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rakeen70210/peer-agents-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server