Skip to main content
Glama
Sign In
copilot-mcp-server

copilot-mcp-server

by x51xxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list-sessions

List, delete, or clear session data for multi-turn conversations to manage conversation continuity.

Instructions

List, delete, or clear session data for multi-turn conversations

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoAction to perform: list, delete, or clearlist
sessionIdNoSession ID for delete action

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits such as destructive nature of delete/clear actions, authentication requirements, or data retention policies. The actions are listed without warnings or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the tool's purpose. It is front-loaded and contains no fluff, making it easy to parse. However, it could be slightly more structured to separate actions.

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's simplicity (2 params, no output schema), the description provides adequate context that it handles session management. However, it omits details about parameter dependencies (e.g., sessionId only for delete) and output format, leaving room for misinterpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents parameter meanings. The description does not add meaningful semantics beyond what the schema provides, merely restating the actions. Baseline score of 3 is appropriate.

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 tool can list, delete, or clear session data for multi-turn conversations. It uses specific verbs and identifies the resource (session data), distinguishing it from sibling tools which cover different functionalities.

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

Usage Guidelines3/5

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

The description implies the tool is used for managing session data, but provides no explicit guidance on when to use it versus other tools or when not to use it. No alternatives are mentioned, which is acceptable given sibling diversity.

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

Deploy Server

Other Tools