Skip to main content
Glama

get_bot_issue

Read-only

Retrieve a specific bot issue by task ID and issue ID to inspect its state and supporting context for debugging or review.

Instructions

get bot issue

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

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.1

TDQS

D1.3/5.0
Behavior1/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 by structured fields. The description adds no behavioral context whatsoever: no note on what a bot issue contains, whether missing IDs error, whether pagination fields apply, or what the caller should expect on failure.

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 the brevity is under-specification rather than economy; the phrase carries no front-loaded information and no structure at all.

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 2 parameters, a nested seven-field object, and no output schema, this definition is far below the minimum needed to call it confidently. Required vs optional, the meaning of the nested fields, and the result shape are all unaddressed.

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 payload is non-trivial: a nested arguments object with after, basis, limit, intent, state_id, plus top-level idempotency_key. None of these are explained anywhere, so the agent must guess what basis, intent, or after mean and whether idempotency_key matters for a read.

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?

"get bot issue" merely restates the tool name with no verb specificity beyond "get" and no statement of what a bot issue is or how retrieval differs from the sibling list_bot_issues. An agent learns only that some issue-shaped resource is fetched, not its scope.

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

Usage Guidelines1/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 prerequisites, and no named alternative such as list_bot_issues. Nothing tells the agent when this retrieval is the right call versus listing issues or fetching bot context.

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