Skip to main content
Glama
boaviztapi-mcp

boaviztapi-mcp

List impact criteria

list_impact_criteria
Read-onlyIdempotent

List BoaviztAPI impact criteria with their code, unit and meaning to decode result codes or pick criteria for estimate tools. Filter by code, unit or keyword such as 'water'.

Instructions

List BoaviztAPI's impact criteria with their code, unit and meaning, e.g. gwp (climate change, kgCO2eq), adp (abiotic resources, kgSbeq) or pe (primary energy, MJ).

Use it to explain a code that appears in a result, or to choose criteria for the estimate tools; it estimates nothing. query filters on code, unit or description words such as 'water'. Read-only; the list comes from BoaviztAPI and is cached for a day.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filter on code or description, e.g. 'water'.

Output Schema

NameRequiredDescriptionDefault
summaryYes
criteriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is not the description's job. It still adds real behavioral context beyond the annotations: the data originates from BoaviztAPI and is cached for a day, which tells the agent the results may be stale. It does not discuss failure modes (e.g. what happens if the upstream API is unreachable, despite openWorldHint), so this is good added context rather than complete disclosure.

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-loaded with the resource and what it returns, followed by usage, then the filter, then operational notes, so structure is good. The single example list is dense but earns its place; the stray line wrapping in the first sentence is cosmetic rather than wasteful.

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?

There is an output schema, so return values need not be spelled out. Combined with source, caching, filter semantics and explicit non-overlap with the estimate tools, an agent has everything required to call this correctly.

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 100%, so the baseline is 3 and the schema already documents `query`. The description goes slightly beyond it by saying the filter matches code, unit or description words and giving 'water' as an example, whereas the schema only mentions code and description. Useful but marginal.

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 and resource ("List BoaviztAPI's impact criteria") plus the fields returned (code, unit, meaning), and gives concrete examples (gwp/kgCO2eq, adp/kgSbeq, pe/MJ). It also explicitly contrasts itself with the estimate tools by saying it estimates nothing, so an agent can separate it from the estimate_* siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete use cases: explaining a code that appears in a result, or picking the `criteria` value for the estimate tools. It closes the loop with an explicit negative boundary ("it estimates nothing"), which is exactly the disambiguation an agent needs when estimate_* tools are present.

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