Skip to main content
Glama
Sign In
ForgeMCP

ForgeMCP

by hardened-steel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debugger_sessions

Read-only

List a bounded window of retained debugger session snapshots for paged inspection of recent debugging activity.

Instructions

List a bounded window of retained debugger session snapshots.

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": "debugger_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo

Output Schema

NameRequiredDescriptionDefault
sessionsYes
next_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that only retained snapshots are returned and that results are bounded, but says nothing about ordering, whether live sessions are excluded, or what happens when the window is exhausted.

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?

A single front-loaded sentence with no filler or redundancy; the scope qualifier and the boundedness constraint are both stated up front.

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

Completeness2/5

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

For a debugger-domain resource whose terminology ('session snapshots') is unusual, one sentence leaves key questions open: what a retained snapshot is, how sessions enter retention, result ordering, and how this relates to debugger_get or debugger_launch. An output schema exists, so return shape need not be described, but the conceptual gaps remain.

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 description coverage is 0% and the single 'page' parameter is undocumented at the property level, but the schema itself supplies defaults, bounds, and a PageRequest description. The phrase 'bounded window' loosely corroborates the page-window semantics without explaining null/default behavior, so it only partially compensates.

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 names a specific verb and resource ('List ... debugger session snapshots') plus a scope qualifier ('retained', 'bounded window'), which distinguishes it from single-object siblings like debugger_get. It stops short of naming an alternative sibling explicitly, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to debugger_get for fetching a single session or to debugger_launch/attach for creating one. Usage is only weakly implied by the word 'List'.

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