Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Set a day's cooking time

set_max_cooking_time_for_date

Add a rule for one date: at most this many active minutes at the stove. The answer's undo deletes the rule again.

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": {
      "date": "<date>",
      "minutes": "<minutes>",
      "strength": "<strength>"
    },
    "name": "set_max_cooking_time_for_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe date, ISO date.
minutesYesMaximum active minutes at the stove.
strengthYesSoft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend on a tight week — including a bare statement said in passing («Taco på fredager», «Fisk to ganger i uka», «Maks 30 minutter på hverdager») and helst/gjerne/prøv. «Maks», «minst» and a number name the limit, not its strength: they do not make a rule Hard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is already covered. The description adds genuine value beyond them by disclosing reversibility ('the answer's undo deletes the rule again'), which is not expressed anywhere in the annotations. It does not address what happens on a repeat call for the same date, which matters given idempotentHint=false.

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?

Two short sentences with the scope and the cap front-loaded before the reversibility note; nothing is padded. The phrase 'The answer's undo' is slightly oblique and costs a moment of parsing.

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?

For a three-parameter rule-creation tool with full schema coverage, an explicit enum, and annotations covering the safety profile, the description supplies the remaining essentials: what is created, its per-date scope, and how to reverse it. No output schema exists, and the return value is addressed indirectly through the undo note.

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 coverage is 100% and the 'strength' parameter is documented in exceptional depth in the schema itself, so the schema carries the semantic load. The description only restates the meaning of 'minutes' ('at most this many active minutes at the stove') and adds nothing about 'date' or the Hard/Soft distinction.

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 and resource: 'Add a rule for one date: at most this many active minutes at the stove.' The 'for one date' scope hints at the distinction from the sibling upsert_max_cooking_time_rule, but that tool is never named, so the agent must infer which one applies.

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?

The date-scoped nature implies when this tool fits, but there is no explicit when-to-use guidance and no comparison to upsert_max_cooking_time_rule or delete_rule, both of which live in the same sibling set. Usage must be inferred from the scope phrase.

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