bunpro-mcp

get_ghost_details

Retrieve ghost review items that remain in your Bunpro review queue after being burned, filtered by reviewable type.

Instructions

Get ghost review items (items that haunt your review queue after being burned).

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": {
      "reviewable_type": "<reviewable_type>"
    },
    "name": "get_ghost_details"
  }
}

Input Schema

Name	Required	Description	Default
`reviewable_type`	Yes	Type of reviewable item

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. It explains the concept of ghost items but does not disclose whether the tool is read-only, requires authentication, or has any side effects. The behavior is implied as a read operation, but lacks explicit transparency.

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

Conciseness4/5

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

The description is a single sentence that immediately states the core function ('Get ghost review items') and then adds a clarifying parenthetical. It is concise and front-loaded, with no extraneous information.

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?

For a simple tool with one required parameter and no output schema, the description provides the essential concept. However, it omits details about return format, pagination, or how ghost items relate to other review states, leaving gaps in contextual understanding.

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?

The input schema has 100% coverage, with the 'reviewable_type' parameter already described as 'Type of reviewable item' and an enum list. The description adds no extra meaning or context for the parameter, so it meets the baseline but does not exceed it.

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 tool's action ('Get ghost review items') and explains the specific concept of ghost items as 'items that haunt your review queue after being burned.' This distinguishes it from other get tools that retrieve active reviews or due counts, though it could be more explicit about the scope.

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?

No guidance is provided on when to use this tool versus its siblings (e.g., get_queue, get_reviews). There is no mention of prerequisites, context, or alternatives, leaving the agent to infer usage without support.

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