Skip to main content
Glama

Get ONES Bug Detail

get_bug_detail
Read-onlyIdempotent

Retrieve bug body, fields, and related task facts by providing a task ID.

Instructions

Get bug body, fields, and related task facts by task id. Prefer get_bug_detail_by_ref when starting from a bug number or URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
team_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYes
descriptionYes
severityYes
priorityYes
related_tasksYes
raw_payloadYes
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint; description adds 'related task facts' but no additional behavioral disclosure. Satisfactory but not enhanced beyond annotations.

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?

Two sentences, front-loaded with purpose, zero filler. Every word earns its place.

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?

Clear purpose and usage guide, but omits explanation of team_id and what 'related task facts' entails. Output schema exists but description could better differentiate from siblings like get_task_messages.

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

Parameters2/5

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

Schema has 0% description coverage. Description explains task_id implicitly ('by task id') but does not mention team_id at all, leaving its purpose unclear.

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

Purpose5/5

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

Specifies verb 'Get', resource 'bug detail', and adds scope 'body, fields, related task facts'. Distinguishes from sibling get_bug_detail_by_ref by noting when to prefer that alternative.

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

Usage Guidelines4/5

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

Explicitly advises using get_bug_detail_by_ref when starting from bug number/URL, providing clear context. Does not cover when not to use or compare to other siblings.

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/twodogwang/mcp-demo'

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