Skip to main content
Glama

Where is the model number

find_model_number
Read-onlyIdempotent

Tells where the rating plate (model number label) is on an appliance and which number to copy for each brand (E-Nr. for Bosch/Siemens/Balay, PNC for AEG/Electrolux/Zanussi, 12NC for Whirlpool, Model for Samsung/LG…), with an example of the format.

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": {
      "appliance": "<appliance>"
    },
    "name": "find_model_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand, e.g. Bosch, Balay, Siemens, Samsung, LG, AEG, Electrolux, Zanussi, Whirlpool, Indesit, Beko, Candy, Teka.
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
applianceYesAppliance: lavadora (washing machine), lavavajillas (dishwasher), secadora, frigorifico, horno, placa, campana, microondas. Free text is fine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already state that the tool is read-only, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds genuinely useful behavior: the answer is brand-specific and identifies the correct number type per manufacturer, with a format example. It does not say what happens when the brand or appliance is unknown, nor how verbose the answer is, so it stays at 3.

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?

It is a single dense sentence, front-loaded with the core action (locating the rating plate) and followed by the brand-specific detail in a parenthetical. Nothing is redundant. The nested parenthetical list of brands and number codes is slightly heavy but earns its space by conveying the mapping.

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?

With three well-documented parameters, a complete schema, and annotations covering the safety profile, the definition supplies what an agent needs to call it correctly. It also signals that the response includes a format example. A note on fallback behavior for unknown brands or appliances would close the 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 description coverage is 100%, so the baseline is 3. The description reinforces the brand parameter by naming the number types (E-Nr., PNC, 12NC) that each brand uses, which is meaning the schema does not carry. It adds nothing about the appliance or language parameters, which the schema already explains well.

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 description gives a specific verb and resource: it tells the user where the rating plate is located on an appliance and which number to copy for each brand. That is concrete and unambiguous. It stops short of naming a sibling such as find_spare_part or diagnose_error_code to contrast against, so it earns a 4 rather than a 5.

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 usage is only implied: the reader can infer the tool is used when they need to locate a model number before searching for parts or filing a warranty claim. There is no explicit when-to-use statement, no exclusion, and no routing to an alternative sibling. For a reference-lookup tool this is adequate but leaves the agent to reason about ordering.

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