Skip to main content
Glama

dieAnalysten Adressshop – German B2B company addresses

branchen_suchen

Read-only

Branchen finden, die im Adressshop verfügbar sind (Stichwort oder Branchengruppe). Ohne Angabe: die Branchengruppen.

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": "branchen_suchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sucheNoz. B. „Steuerberater“, „Bäckerei“
gruppeNo

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the default outcome when no argument is supplied, which is genuine behavior beyond the annotations, but it says nothing about result count, result shape, or whether the lookup is exact or substring matching.

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?

Two short sentences with the resource and the fallback behavior front-loaded; no filler and no restatement of the tool name. Every clause carries information an agent needs.

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 two-parameter, read-only lookup with no output schema, the definition covers the essentials but leaves the return type and the semantics of gruppe ambiguous. An agent could invoke it, but may not know what the results look like or how to use them downstream.

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 50%: suche carries examples in the schema while gruppe has no description at all. The description partially compensates by stating the two lookup modes (Stichwort vs. Branchengruppe) and by clarifying that omitting both returns the groups, but it never says whether gruppe takes a name, an ID, or a group key.

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?

Names a specific verb+resource ("Branchen finden, die im Adressshop verfügbar sind") and even the lookup axis (Stichwort oder Branchengruppe). Siblings (bestellung_anlegen, preis_berechnen) are clearly different operations, so an agent can distinguish it without opening the schema, though the description never explicitly contrasts itself with them.

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?

"Ohne Angabe: die Branchengruppen" implies the no-argument case (call bare to enumerate groups), which is a useful usage cue. However, there is no statement of when to prefer this over siblings (e.g. as a precursor to preis_berechnen or zielgruppe_zaehlen) and no guidance on how suche and gruppe interact or whether they can be combined.

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