Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Choose stores

select_stores
DestructiveIdempotent

Set the stores the household shops at. This replaces the whole selection, so name every store they want; get_stores shows the ones chosen now. Bryti looks the names up near the household's address, and a name it does not find fails with the stores nearby.

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": {
      "storeNames": "<storeNames>"
    },
    "name": "select_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoAddress the stores are near; omit when they are near the household's own address.
storeNamesYesThe stores to shop at.
storeAddressesNoOnly for an undo: the address each store was found near, in the same order as storeNames.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description goes further by explaining exactly what is destroyed (the whole prior selection is replaced) and how resolution works (names are looked up near the household's address, and a miss fails with nearby stores returned). The main gap is that success behavior/return value is never mentioned, which matters for a no-output-schema tool.

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?

A compact three-sentence block with the replacement warning front-loaded before the lookup/failure caveat. Dense but every sentence carries necessary semantics; only the slightly run-on final sentence costs it a point.

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 3-parameter mutation with no output schema, the description covers scope, replacement semantics, lookup behavior and the failure mode, which is most of what an agent needs. The one omission is what a successful call does or returns, leaving the agent to infer success silently.

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 real meaning beyond the schema: it explains that names are resolved geographically relative to the household address, which clarifies why 'address' exists and why exact names from find_stores matter. It does not elaborate on storeAddresses ordering beyond what the schema already says.

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?

States a specific verb and resource ('Set the stores the household shops at') and explicitly positions it against the read sibling get_stores, which 'shows the ones chosen now'. An agent can distinguish this write tool from the read tool without consulting either schema.

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?

Gives the critical operating guidance up front: the call replaces the entire selection, so every desired store must be named, and points to get_stores for the current state. It does not spell out a when-not-to-use or the undo path (storeAddresses) in prose, leaving that to the schema, so it falls short of a full 5.

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