Flash

Set limits

set_limits

Idempotent

Use this when the user wants to change how many new cards or reviews they get per day, for every deck or for one, or gives the date they need to know a deck by (an exam, a test, a deadline): goal_date paces that deck toward it. Without a deck it sets the account defaults; with a deck it sets that deck's override (-1 clears it so the deck inherits the account default). Omitted fields are left unchanged. For extra new cards today only, use boost_new_today.

Input Schema

TableJSON Schema

Name	Required	Description
`deck`	No	Deck name to set an override for; omit to set the account defaults.
`goal_date`	No	With a deck only: the date the user needs to know it by (an exam, a test, a trip, a deadline), YYYY-MM-DD on their calendar. Flash paces the deck's new cards to finish before it and brings back, in the last days, the cards that need it. An empty string clears it; omit to leave it unchanged.
`new_per_day`	No	New cards per day. Omit to leave unchanged; for a deck, -1 clears the override so it inherits the account default.
`reviews_per_day`	No	Max reviews per day. Omit to leave unchanged; for a deck, -1 clears the override so it inherits the account default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`saved`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / goal_date

Added value: +{
+  "default": null,
+  "description": "With a deck only: the date the user needs to know it by (an exam, a\ntest, a trip, a deadline), YYYY-MM-DD on their calendar. Flash paces\nthe deck's new cards to finish before it and brings back, in the\nlast days, the cards that need it. An empty string clears it; omit\nto leave it unchanged.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedSep 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=true; the description adds meaningful behavioral context beyond that — omitted fields are left unchanged, -1 clears a deck override so it inherits account defaults, and an empty string clears goal_date. This inheritance/clearing semantics is valuable, though some of it is echoed from the schema text.

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?

Dense but front-loaded: the trigger condition leads, followed by the deck/account branching, clearing semantics and the alternative tool. Slightly long and packs several clauses, but nearly every sentence carries distinct information.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description fully covers the account-default vs deck-override branching, reset semantics, and the sibling alternative. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents every parameter including the -1 and empty-string clearing rules. The description reinforces the deck/goal_date relationship and the clearing behavior but adds little that isn't already in the schema, so the baseline 3 applies.

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?

States a specific verb and resource (set daily new/review limits, per-deck or account-wide) and immediately distinguishes itself from the sibling boost_new_today for same-day extra cards. An agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicitly says "Use this when the user wants to change how many new cards or reviews they get per day" and names the alternative (boost_new_today) with its distinguishing condition (extra new cards today only). It also covers the goal_date use case and the no-deck vs with-deck branches.

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

All Flash tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.