Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Find an area

find_areas
Read-onlyIdempotent

Find an area from a place as written: region, département, commune, postal code, or a radius around a town ("Lyon", "33", "30 km around Nantes"). Use the "area" field of a result (or of "match" when its status is "resolved") as the area of suggest_categories or as search.area.

Free.

Same call as GET /api/v1/areas of the REST API.

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": {
      "q": "<q>"
    },
    "name": "find_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesA place as written: "Lyon", "31000", "Gironde", "within 30 km of Nantes", "the South-West".
levelNoOnly this level of area.
limitNoAreas returned (default 10, at most 20).
countryNoSearch this country only (ISO alpha-2, lower case). Default: every open country.
radiusKmNoA radius around the place, in km (1 to 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world semantics, so the description adds the cost profile ("Free") and a partial return shape (an "area" field, plus "match" with a "resolved" status) that no output schema provides. It still leaves ambiguous-result handling and error behavior unexplained.

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 core capability and its inputs are front-loaded in one dense sentence, with integration guidance next. The "Free." and REST-endpoint lines are short and useful, though the endpoint mapping serves developers more than an agent choosing a tool.

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 five-parameter lookup with no output schema, the definition supplies input forms, cost, result-field semantics, and a downstream consumer. Gaps remain around what an unresolved/ambiguous match means and what to do when multiple areas return, but the essentials for correct invocation are present.

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 applies. The description's free-text form hints ("33", "30 km around Nantes") loosely reinforce q and radiusKm, but it says nothing about level, country, or limit, so it adds little beyond the schema's own descriptions.

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?

Specific verb plus resource: "Find an area from a place as written," followed by the accepted input forms (region, département, commune, postal code, radius around a town) and concrete examples. It also names the consumer tools (suggest_categories, search.area), which distinguishes it from the category/network search siblings.

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?

It explains the downstream workflow clearly: feed the "area" field (or "match" when status is "resolved") into suggest_categories or search.area. What's missing is any when-not guidance, e.g. whether to skip it when an identifier is already known, or how it relates to find_categories/find_networks.

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

All Primavera 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