Skip to main content
Glama

list_bot_issues

Read-only

Retrieves bot issues for a specified task ID, with pagination and optional filters for state, intent, or basis, to support issue review and tracking.

Instructions

list bot issues

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "arguments": "<arguments>"
    },
    "name": "list_bot_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.1

TDQS

D1.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description contributes nothing beyond that — no pagination behavior, no mention of what 'issues' contain or how states filter results — so it fails to enrich what the annotations provide.

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

Conciseness2/5

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

It is short, but only because it is under-specified rather than efficient — three words that add no information beyond the tool name. There is no structure or front-loaded detail to speak of.

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

Completeness1/5

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

For a tool with nested object parameters, a required task_id, optional pagination and state filters, and no output schema, a three-word description is wholly inadequate. Nothing tells the agent what to pass or what to expect back.

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

Parameters1/5

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

Schema description coverage is 0% and the input has a nested arguments object with six properties (task_id, state_id, basis, intent, after, limit) plus an idempotency_key. The description mentions none of these, leaving opaque parameters such as 'basis' and 'intent' entirely unexplained.

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

Purpose2/5

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

The description reads "list bot issues", which essentially restates the tool name and adds no scope, resource qualifiers, or distinguishing detail. An agent cannot tell from this whether it lists issues assigned to a bot, issues discovered by a bot, or something else, nor how it differs from the sibling get_bot_issue.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as get_bot_issue for fetching a single issue. The agent must infer usage entirely from the name and the required task_id parameter.

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