Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Space out the same dish

upsert_repeat_after_days_rule
Idempotent

Set how many days must pass before the same dish comes back, 3 to 30. Bryti's default is 10. 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": {
      "days": "<days>",
      "strength": "<strength>"
    },
    "name": "upsert_repeat_after_days_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesDays between two servings of the same dish, 3–30.
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 already mark this as non-read-only, idempotent and non-destructive; the description corroborates idempotency by explaining that a matching rule is overwritten rather than duplicated. It also discloses the mutation consequence that the strength setting defaults to Soft and only becomes Hard on explicit household insistence, which is real behavioral context not carried by the annotations. It does not say what an invalid or out-of-range value does.

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 short sentences, front-loaded with the constraint and range before the upsert and strength caveats. The closing sentence largely echoes the enum description in the schema, which is mild redundancy but brief enough not to hurt.

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 two-parameter mutation with no output schema and full annotation coverage, the description covers range, default, dedup behavior and the strength default policy — enough to call it correctly. Minor gaps are error behavior and explicit sibling routing among the other upsert_*_rule tools.

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, and the description adds the one thing the schema omits: the current default of 10 days. It otherwise restates the range and the Soft-by-default posture already documented in the strength enum.

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 — setting the number of days before the same dish repeats — which implicitly separates it from the category-level siblings (upsert_category_frequency_rule) by naming 'the same dish'. Clear to an agent, though it never names a sibling outright to route against.

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?

Explains the upsert contract ('a rule about the same thing is changed, not added twice') and supplies the 3–30 bounds plus the default of 10, which is useful calling context. It gives no explicit guidance on when to use this versus the other upsert_*_rule tools or when to prefer a Hard rule over leaving the default.

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