Skip to main content
Glama

Alle Providers

Zoek in de gidsen

zoek_gids
Read-onlyIdempotent

Search the alle-providers.nl guides, provider pages and comparisons (Dutch): switching provider, fiber installation, modems, network fees, a specific provider. Zoekt in de gidsen en providerpagina’s. Geeft titels, links en de passende alinea’s.

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": {
      "vraag": "<vraag>"
    },
    "name": "zoek_gids"
  }
}

Input Schema

NameRequiredDescriptionDefault
vraagYesSearch terms or question, Dutch works best.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds value beyond that by stating what comes back: titles, links and the matching paragraphs ('Geeft titels, links en de passende alinea’s'), which matters since there is no output schema. It does not mention result limits, ranking behavior or rate limits, keeping it short of a 5.

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?

The English sentence is front-loaded with the corpus and then the topics, and the closing Dutch sentence adds the return-value detail. The Dutch half partly restates the English half ('Zoekt in de gidsen en providerpagina’s'), which is mild redundancy but justifiable for a bilingual audience; nothing else is wasted.

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 search tool with full schema coverage and a complete annotation set, the description supplies what is missing: the searched sources, example subject domains, and the shape of the results. The only material gap is sibling disambiguation against zoek_aanbod, which would matter for an agent choosing between content search and offer search.

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?

With a single parameter at 100% schema description coverage, the schema already explains that it takes search terms or a question and that Dutch works best. The description reinforces this by listing the Dutch-language subject areas that make good queries, which helps query formulation, but it adds no syntax, length or formatting guidance 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 names a specific verb (search) and a specific corpus (alle-providers.nl guides, provider pages, comparisons) and enumerates concrete topics such as switching provider, fiber installation, modems and network fees. This is far more precise than a generic 'search' label, though it never explicitly contrasts itself with the sibling zoek_aanbod, so an agent must infer that this searches editorial content rather than offers.

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 topic list (switching, fiber installation, modems, network fees, a specific provider) implicitly signals the kinds of questions this tool is for, which is real usage guidance. However, there is no explicit when-not-to-use statement and no mention of when to prefer zoek_aanbod or aansluitingen, leaving the routing decision 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