Skip to main content
Glama

search_content

Read-onlyIdempotent

Zoek in publieke renovatie-informatie voor Vlaanderen. Geeft canonieke bronnen; lees de pagina en primaire bronnen voor veranderlijke regels.

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": {
      "query": "<query>"
    },
    "name": "search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 a useful behavioural nuance: results are canonical sources, and volatile rules must be verified by reading the underlying page/primary sources. It says nothing about result volume or the effect of 'limit'.

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?

Two short sentences, front-loaded with the resource and followed by the retrieval advice; nothing is wasted. The terseness comes at the cost of content rather than verbosity, but structurally it is efficient.

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 simple two-parameter search tool with no output schema, the description at least indicates the return type (canonical sources) and the follow-up workflow. It falls short on query formulation and on limit semantics, which are the main things an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both 'query' and 'limit' rely on the description for meaning, and the description mentions neither. It does not say what language or format the query should take (natural-language question, keyword, URL?) nor what 'limit' bounds, leaving the agent to guess from 'default 5, maximum 10'.

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?

States a specific verb and resource: searching public renovation information for Flanders, and notes it returns canonical sources. This distinguishes it clearly from the calculate_* siblings, though it never names them, and the scope ('publieke renovatie-informatie voor Vlaanderen') is concrete enough for an agent to recognise.

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 second clause implies a follow-up path ('lees de pagina en primaire bronnen voor veranderlijke regels'), effectively pointing at read_page for changeable rules. However, there is no explicit guidance on when to use this versus the calculator siblings, and no exclusion or prerequisite stated.

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