Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Set prep days

set_prep_days
Idempotent

Set the weekdays the household preps ahead for the week, and the hour it starts. Steps a recipe allows to be done early are then shown on the latest prep day that keeps them fresh. An empty weekdays list turns prep days off. freezesPrep lets steps that keep frozen go to an earlier prep day.

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": {
      "weekdays": "<weekdays>"
    },
    "name": "set_prep_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoWhen prep starts on those days, 24-hour HH:mm. Omit to keep the hour the household has (15:00 when it has none).
weekdaysYesThe prep days. Empty turns prep days off.
freezesPrepNoTrue when the household freezes what keeps frozen, so it can be made on an earlier prep day. Omit to leave it as it is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive, closed-world), the description explains important behavioral consequences: empty weekdays disables prep days, early steps are shown on the latest prep day that keeps them fresh, and freezesPrep alters scheduling for frozen items.

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?

The description is front-loaded with the core action and then adds relevant behavioral notes in four economical sentences with no wasted wording.

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 three-parameter mutation tool with no output schema, the description covers the main purpose and key side effects (disabling via empty list, scheduling logic, freeze handling), though it could say more about applicability to existing plans.

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?

The schema already documents all three parameters at 100% coverage, and the description adds little meaning beyond what is in the schema for weekdays, time, and freezesPrep; baseline 3 is appropriate when schema carries the detail.

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 gives a specific verb ('Set') and resource ('the weekdays the household preps ahead for the week, and the hour it starts'), clearly distinguishing this configuration tool from siblings like set_dinner_time or set_dinner_lock.

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?

Usage is implied by the direct instruction to set prep days and the note that an empty list turns them off, but there is no explicit when-to-use guidance or mention of alternatives or exclusions.

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

All Bryti toolsInspect
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.

Resources