Skip to main content
Glama
Sign In

Bryti

by app.bryti
OverviewDiscussionsAdmin

Kitchen tips

search_tips
Read-onlyIdempotent

Search Bryti's fact-checked kitchen tips.

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": {
      "query": "<query>"
    },
    "name": "search_tips"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe cooking question in a few words, in the household's own language — the food and what happened or what they want to do («gryte for salt», «steak rest», «freeze potatoes»).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false. The description adds only that tips are 'fact-checked'; it does not explain result format, search limits, or matching behavior beyond the query schema.

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?

One front-loaded sentence with no filler, repetition, or buried details. It is appropriately sized as a concise tool summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only search, the description plus annotations and schema cover the basic invocation. However, with no output schema, the result shape is not described, and the missing differentiation from search_help leaves selection context incomplete.

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 description coverage is 100%, and the query parameter is richly documented with household-language guidance and examples. The description adds no parameter meaning beyond 'Search Bryti's fact-checked kitchen tips', so the baseline score of 3 applies.

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 ('Search') and resource ('kitchen tips'), plus the quality qualifier 'fact-checked'. It is clear what the tool does, but it does not explicitly distinguish itself from sibling search-like tools such as search_help.

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

Usage Guidelines2/5

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

Gives no when-to-use condition, no when-not condition, and no named alternative. An agent must infer from the word 'kitchen' and the query schema that this is for cooking questions, while the relationship to search_help is left unaddressed.

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