Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

urba_risques

Natural & technological risks recorded for a commune (Géorisques GASPAR).

Returns distinct long labels: flooding, ground movement, clay shrink-swell, seismicity, hazardous-materials transport, ICPE/Seveso… Empty list if none recorded. Takes the INSEE commune code (5 chars).

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": {
      "code_insee": "<code_insee>"
    },
    "name": "urba_risques"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
code_inseeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the data source (GASPAR), the granularity (distinct long labels, i.e. deduplicated), and empty-result behavior. It does not state that the operation is read-only, nor any coverage limits, latency, or whether results are cached — details an agent would want before relying on it in a pipeline.

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?

Four short sentences, front-loaded with purpose, then output shape, then failure mode, then input. Every sentence carries information; no preamble or filler.

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 single-purpose read lookup with no output schema, the description covers what is returned (labeled risk categories), the empty case, and the input format — enough to call it correctly without prior knowledge. Missing only an explicit read-only/safety statement and overlap handling with the nearby argiles/ICPE tools.

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 83% and code_insee itself is undocumented in the schema, so the description's 'Takes the INSEE commune code (5 chars)' adds real value, including the format constraint. Beyond that it adds nothing about the platform parameters (_org, _group, _run_id, _project, _instance), which are documented in 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?

States a specific verb+resource ('Natural & technological risks recorded for a commune') and names the authoritative source (Géorisques GASPAR). It enumerates the returned risk categories, so an agent knows exactly what it gets. It stops short of naming siblings such as urba_argiles, which covers one of the listed categories (clay shrink-swell), so the boundary against neighbors is implied rather than stated.

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?

Usage is implied: pass a commune's INSEE code and get its recorded risks; the 'empty list if none recorded' note tells the agent how to read a null result. There is no explicit when-to-use/when-not guidance and no pointer to alternatives (urba_argiles, urba_icpe/foncier_icpe) for the overlapping risk categories.

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

All Tulina toolsInspect
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