Skip to main content
Glama
Sign In
Bunpro MCP

Bunpro MCP

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_daily_forecast

Read-onlyIdempotent

Retrieves the user's daily review forecast from Bunpro so you can plan study sessions and see upcoming reviews.

Instructions

Get the daily review forecast

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_daily_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/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. However, the description adds nothing beyond that — it does not clarify the forecast horizon (today only? next 24h?), timezone handling, or what the 'forecast' contains, all of which matter for a no-parameter read.

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?

A single front-loaded sentence with no wasted words. Its brevity is efficient, though it shades into under-specification rather than crispness.

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, the description is the only place to learn what a 'daily review forecast' returns (per-day counts? per-SRS-stage breakdown? date range?). It supplies none of that, and the sibling get_hourly_forecast makes the missing granularity distinction costly.

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, which is the baseline-4 case. The description correctly implies no inputs are needed to scope the daily forecast.

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?

States a specific verb ('Get') and resource ('daily review forecast'), so the agent knows this returns forecast data. It does not explicitly distinguish itself from the sibling 'get_hourly_forecast', though the word 'daily' hints at the granularity difference.

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?

There is no guidance on when to use this versus get_hourly_forecast, get_due, or get_queue, all of which sound adjacent. The agent is left to infer usage entirely from the name.

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