Geo-Insights Environmental Data

Search BGI Measures

search_bgi_measures

Read-onlyIdempotent

Search the Blue-Green Infrastructure measure catalog (44 measures).

All parameters are optional — call with no args to list all measures.

Args:
    goal: Filter by climate goal: flood, heat, drought, biodiversity, social
    category: Filter by category: water_retention, heat_mitigation,
              surface_water, biodiversity
    keyword: Search in name, Dutch name, and description (e.g. "dak", "roof")
    limit: Max results (default 20, max 50)

Returns measures with goal scores, category, scale, and maintenance level.
Use get_measure_detail for full specs on a specific measure.

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

Input Schema

Name	Required	Description	Default
`goal`	No
`limit`	No
`keyword`	No
`category`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`measures`	Yes
`last_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior is covered. The description adds the catalog size, the default (20) and hard max (50) limit, and the shape of returned records (goal scores, category, scale, maintenance level), which are useful operational constraints beyond the annotations.

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?

Front-loads the one-line purpose, then a no-arg usage note, then a compact per-parameter block, then return/next-step guidance. Every sentence earns its place; only the docstring-style 'Args:' formatting is slightly less scannable than prose.

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 optional-filter search tool with annotations covering safety and an output schema covering return values, the description supplies everything else an agent needs: no-arg behavior, filter domains, result cap, and the hand-off to get_measure_detail.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: it enumerates the allowed goal values (flood, heat, drought, biodiversity, social), the allowed category values, which fields keyword searches (name, Dutch name, description) with examples, and the limit default and maximum. This goes well beyond the bare schema properties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (Blue-Green Infrastructure measure catalog) plus the catalog size (44 measures). It also explicitly routes to get_measure_detail for full specs, so an agent can distinguish it from that sibling without inspecting either schema.

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?

Explicitly says all parameters are optional and that a no-arg call lists all measures, and it names get_measure_detail as the alternative for full specs. It does not say when to prefer this over ranking or comparison siblings, so the guidance is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Geo-Insights Environmental Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?