bunpro-mcp

get_item

Retrieve full details of a Bunpro grammar or vocabulary item by its slug or ID, including meaning, structure, example sentences, and SRS status.

Instructions

Get full details for a grammar point or vocabulary item by its slug or ID (e.g. 'は-wa-topic-marking-particle' or '42'). Returns meaning, structure, example sentences, SRS status, and more.

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": {
      "slug_or_id": "<slug_or_id>"
    },
    "name": "get_item"
  }
}

Input Schema

Name	Required	Description	Default
`slug_or_id`	Yes	Item slug (e.g. 'は-wa-topic-marking-particle') or numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Lists returned fields but does not disclose error handling, auth needs, or rate limits. No contradictions.

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?

Single concise sentence that front-loads purpose and provides example inputs. No wasted words, but slightly more detail on return type could be added without bloating.

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

Completeness4/5

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

For a simple read tool with one parameter and no output schema, the description covers purpose, parameter, and sample returned fields. Missing behavior on non-existent slug/ID.

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?

Schema already describes the single parameter with examples. Description adds examples in context but does not provide additional semantics beyond schema, which has 100% coverage.

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?

Description clearly states verb 'Get' and resource 'full details for a grammar point or vocabulary item', with example inputs. Distinguishes from sibling 'search' by being ID/slug-specific.

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

Usage Guidelines3/5

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

Implies use when slug/ID is known, but does not explicitly state when not to use or mention alternatives like 'search' for fuzzy queries.

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