Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Put a category on a weekday

upsert_category_on_day_rule
Idempotent

Set that a meal category belongs on a weekday every week, e.g. taco on Fridays. One single date is set_category_for_date. 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": {
      "category": "<category>",
      "weekday": "<weekday>",
      "strength": "<strength>"
    },
    "name": "upsert_category_on_day_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekdayYesThe weekday it belongs on, week after week.
categoryYesThe meal category.
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

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior. The description adds the default strength semantics ('Soft unless the household says it must hold') and reinforces upsert behavior, which is useful context beyond the annotations. It does not describe overwrite effects on an existing conflicting rule.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four brief sentences, front-loaded with purpose and example, then the alternative, then the upsert and default rules. There is no padding or repetition that isn't functional.

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 simple three-parameter mutation with full schema descriptions and annotations, the description supplies purpose, the key alternative, and default behavior. It lacks clarity on how this rule interacts with the neighboring frequency and exclusion rule tools, which is the main remaining gap.

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 field already carries extensive enum documentation. The description adds only the example mapping and the Soft default, both of which are already implied or stated in the schema, so it adds little beyond structured fields.

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?

Names the specific operation — a recurring weekly category-to-weekday rule — with a concrete example ('taco on Fridays') and explicitly contrasts it with set_category_for_date for single dates. It does not differentiate itself from the other upsert_*_rule siblings (frequency, excluded days, max time), so an agent could still hesitate among rule tools.

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

Usage Guidelines4/5

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

Provides clear when-to-use context (weekly recurring assignment), names one alternative (set_category_for_date) and explains upsert semantics ('changed, not added twice'). There is no explicit when-not guidance against the other rule siblings, and the strength schema's own example 'Fisk to ganger i uka' is a frequency rule that this description does not address.

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