Skip to main content
Glama

Moja Serowarnia: kultury i przepisy na sery

Zamienniki kultury

zamienniki
Read-onlyIdempotent

Czym zastąpić daną kulturę bakteryjną i co wyjdzie taniej. Kultury o identycznym składzie gatunkowym jak podana, od najtańszej w przeliczeniu na litr mleka. Zaznacza, gdy w grupie są różne przeznaczenia albo różne proporcje szczepów. Ten sam skład nie znaczy ten sam produkt: wynik ma to zastrzeżenie w polu zastrzezenie.

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": {
      "nazwa": "<nazwa>"
    },
    "name": "zamienniki"
  }
}

Input Schema

NameRequiredDescriptionDefault
nazwaYesNazwa handlowa kultury, do której szukamy zamiennika

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral value beyond that: results are ordered by price per litre, groups with mixed purposes or differing strain ratios are flagged, and a 'zastrzezenie' caveat field is included in the response. It does not say what happens when no substitute exists, which is the main remaining gap.

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 purpose and ranking rule before the caveats. Each sentence carries distinct information (what it does, how it ranks, what it warns about), with minimal redundancy between the first and last sentence.

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 one-parameter read-only lookup with annotations and no output schema, the description covers ranking, grouping flags and a caveat field, which is close to complete. Only the empty-result case and the shape of the flag fields are left unstated.

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 single 'nazwa' parameter is already documented as the commercial name of the culture to match. The description restates the same idea ('daną kulturę bakteryjną') without adding format, matching tolerance, or naming-convention detail, so the schema does the heavy lifting.

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 opening clause names a specific verb and resource ('Czym zastąpić daną kulturę bakteryjną' – what to substitute a given bacterial culture with) plus an economic goal ('co wyjdzie taniej'). It also pins the matching rule (identical species composition) and sort order (cheapest per litre of milk), which makes it clearly distinct from lookup siblings like szukaj_kultur, though no sibling is named explicitly.

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?

The substitution/price scenario is implied by the opening sentence, so an agent can infer when to reach for this tool. However, there is no explicit when-not guidance, no mention of prerequisites, and no named alternative for plain culture lookup, leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources