Skip to main content
Glama
Sign In
Bunpro MCP

Bunpro MCP

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_srs_overview

Read-onlyIdempotent

Retrieve an overview of Bunpro SRS levels to track spaced-repetition progress and see how vocabulary is distributed across study stages.

Instructions

Get the SRS level overview

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_srs_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no indication of what the overview aggregates, scope of data covered, or any cost/latency characteristics even though openWorldHint suggests external data.

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

Conciseness3/5

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

The single sentence is terse and front-loaded with no filler, which is structurally fine. However, its brevity comes at the cost of under-specification rather than economy — nothing in the sentence earns its place by informing the agent.

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

Completeness2/5

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

With no output schema and no parameters, the description is the only source of meaning, yet it says nothing about what the 'overview' returns or how it relates to the many SRS sibling tools. For a zero-arg tool in a crowded namespace, this leaves the agent unable to choose confidently.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain. Per the baseline rule for parameterless tools, a 4 is appropriate.

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?

The description 'Get the SRS level overview' essentially restates the tool name (get_srs_overview) with no added specificity about what an 'overview' contains. It does not distinguish this from sibling tools like get_srs_level_details, get_self_study_srs_details, or get_ghost_srs_details, which clearly cover overlapping SRS territory.

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 guidance on when to call this tool versus the several closely related SRS siblings. An agent cannot infer from the text whether 'overview' is a summary view, a prerequisite step, or an alternative to get_srs_level_details.

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

Deploy Server

Other Tools