bunpro-mcp

add_to_reviews

Add vocabulary or grammar points to your Bunpro SRS reviews. Items become reviewable immediately at level 0.

Instructions

Add one or more items to your Bunpro SRS reviews. Items start at SRS level 0 and become reviewable immediately. Note: reviewable_type for this endpoint is 'Vocab' or 'GrammarPoint' (not 'Vocabulary').

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": {
      "reviewables": "<reviewables>"
    },
    "name": "add_to_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`reviewables`	Yes	Items to add to reviews
`deck_id`	No	Optional deck ID; null/omitted = default

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that items start at SRS level 0 and become reviewable immediately, and notes the allowed reviewable_type values. However, it omits other behavioral traits such as authentication requirements, side effects, or rate limits.

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?

The description is two sentences, front-loaded with core purpose, and includes essential behavioral info without redundancy. Every sentence earns its place.

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 mutation tool with 2 parameters and no output schema, the description covers purpose, basic behavior, and parameter nuance. It does not explain return values or error handling, but these are less critical given the tool's straightforward nature.

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

Parameters4/5

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

Schema description coverage is 100%, but the description adds value by clarifying the reviewable_type enum values (e.g., not 'Vocabulary') and explaining that deck_id is optional with default behavior. This goes beyond the schema alone.

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?

The description clearly states the verb 'Add' and the resource 'items to your Bunpro SRS reviews', specifying that items start at SRS level 0 and become reviewable immediately. It also distinguishes from sibling tools like 'remove_from_reviews' and 'get_reviews'.

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?

The description indicates when to use the tool (to add items to reviews) and provides a clarifying note on reviewable_type values ('Vocab' or 'GrammarPoint'). However, it does not explicitly state when not to use or mention alternatives, though the sibling tool list helps.

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