Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Limit time until dinner

upsert_max_total_time_rule
Idempotent

Set the most minutes from the first step until dinner is on the table, oven and resting included, every day or on the weekdays named. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

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

Input Schema

NameRequiredDescriptionDefault
minutesYesMaximum minutes from the first step to the table, 10-240.
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.
weekdaysNoThe weekdays the maximum holds on; omit for every day.

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 already declare idempotentHint=true and destructiveHint=false, but the description adds real value by spelling out what idempotency means here: a rule about the same thing is modified rather than duplicated. It also warns that the strength defaults to Soft for the planner to bend, which is behavioral context not captured in the annotations. It does not say what happens to previously set weekdays when the field is omitted on an update.

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?

Three compact sentences, purpose front-loaded, with no filler or repetition of the name. The final sentence on Soft-vs-Hard overlaps with the schema's strength description, so a small amount of space is spent restating structured content.

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 rule-upsert tool with full schema coverage and annotations, the description covers purpose, scope, default strength, and upsert semantics. The only meaningful omission is update-side behavior — whether omitting weekdays clears prior day restrictions — plus any indication of return value, though no output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by defining the time window as 'from the first step until dinner is on the table, oven and resting included' — clarifying what the minutes parameter counts. The strength default ('Soft unless the household says it must hold') mirrors but reinforces the enum documentation.

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?

The description states a specific verb and resource — set the maximum minutes from first step to table, including oven and resting time — which meaningfully separates it from the cooking-time sibling tools (upsert_max_cooking_time_rule, set_max_cooking_time_for_date). It does not name those siblings explicitly, so an agent must infer the boundary from the 'oven and resting included' phrasing.

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?

It gives useful scoping context ('every day or on the weekdays named') and clarifies upsert semantics — a same-topic rule is changed, not added twice. However, it never says when to use this versus upsert_max_cooking_time_rule or set_max_cooking_time_for_date, and no prerequisites or exclusions are stated.

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