Skip to main content
Glama

Mineral-Check – Haarmineralanalyse, Nagelanalyse, Tierhaaranalyse für Pferd und Hund

find_tests

Read-onlyIdempotent

Search the public German Mineral-Check catalog by German keyword (e.g. Wasser or Hausstaub). Omit query to browse up to 20 products. Returns names and original product links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWonach wird gesucht? Für einen Wassertest „Wasser“ eingeben, für einen Hausstaubtest „Hausstaub“. Ohne Eingabe werden bis zu 20 Produkte angezeigt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, idempotent, non-open-world behavior. The description adds meaningful scope and output context: public German catalog, up to 20 browse results, product names, and original product links.

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?

The definition is three short, front-loaded sentences with no wasted wording. It moves from search behavior to the omit-query case and then return contents.

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

Completeness5/5

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

For a simple read-only, single-optional-parameter search tool with rich annotations, this description covers scope, keyword examples, browse default, result limit, and return contents. Nothing essential for correct invocation appears to be missing.

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 single optional query parameter is already documented in the schema, including German examples and default browse behavior. The description reinforces the German-keyword semantics but adds little beyond the schema.

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 specifies a concrete search action over a named public German Mineral-Check catalog, with example keywords. It is clear what the tool does, though it does not explicitly contrast itself with the sibling shop_information tool.

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?

It explains both search mode by keyword and browse mode when query is omitted, giving the agent clear usage context. It does not state exclusions or when to prefer shop_information instead.

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