Skip to main content
Glama

list_instruments

Display all active debug instruments to monitor and manage code instrumentation during debugging sessions.

Instructions

List all active debug instruments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'list_instruments' tool. It fetches all active instruments using sessionManager.getInstruments() and formats them into a text list, returning it via the MCP response format or a 'No active instruments' message if empty.
    case 'list_instruments': {
      const instruments = sessionManager.getInstruments();
    
      if (instruments.length === 0) {
        return {
          content: [{ type: 'text', text: 'No active instruments.' }],
        };
      }
    
      const list = instruments
        .map((i) => `- ${i.id}: ${i.file}:${i.line} [${i.capture.join(', ') || 'no capture'}]`)
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Active instruments (${instruments.length}):\n\n${list}`,
          },
        ],
      };
    }
  • src/index.ts:93-100 (registration)
    Tool registration entry for 'list_instruments' in the ListToolsRequestHandler response, defining name, description, and empty input schema.
    {
      name: 'list_instruments',
      description: 'List all active debug instruments.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • SessionManager helper method that returns the array of all active Instrument objects stored in the session Map.
    getInstruments(): Instrument[] {
      if (!this.session) {
        return [];
      }
      return Array.from(this.session.instruments.values());
    }
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. It states the tool lists 'active' instruments, which implies a read-only operation, but doesn't clarify what 'active' means, whether there are rate limits, or what the output format looks like. This leaves significant gaps for a tool that likely interacts with debug sessions.

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 that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'active' means in context of sibling tools like debug sessions, nor does it describe the return format, leaving the agent unsure about behavioral details. This is a basic read operation, but more context would help.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score, though it doesn't add extra value beyond the schema's completeness.

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 verb 'List' and the resource 'active debug instruments', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'read_debug_logs' or 'start_debug_session', which prevents a perfect 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 'read_debug_logs' or 'add_instrument'. It lacks context about prerequisites, such as whether a debug session must be active, or exclusions for when other tools might be more appropriate.

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/iarmankhan/agentic-debugger'

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