Sentinelle syndic FR

syndic_echeances

France condominiums whose syndic mandate ends soon, by area. For a commune (INSEE code), postal code, department or a syndic's SIRET, and a date window (default next 6 months): up to 100 condominiums per call, sorted by mandate end date, with current professional syndic, lots and address, from the official ANAH registry. Prospect list for property managers, insurers, contractors. Price: 0.03 USDC per call (x402).

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

Input Schema

Name	Required	Description	Default
`apres`	No
`avant`	No
`commune`	No
`decalage`	No
`lots_min`	No
`code_postal`	No
`departement`	No
`type_syndic`	No
`siret_syndic`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the data source (official ANAH registry), the 100-result cap per call, sort order by mandate end date, the default six-month window, the returned fields (syndic, lots, address), and a payment requirement (0.03 USDC per call via x402). It does not cover failure modes, rate limits, or how to page beyond 100 results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph with the resource front-loaded, followed by inputs, output shape, audience, and price in that order. Every clause carries information; nothing is redundant padding.

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 nine-parameter, no-annotation, no-output-schema tool, the description covers the domain, source, cost, limits, and return fields well, but the omission of decalage, lots_min, and type_syndic leaves real gaps an agent cannot resolve without guessing. Adequate but not complete for the tool's complexity.

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 description coverage is 0%, so the description must compensate for nine undocumented parameters. It explains commune as an INSEE code and groups commune/postal code/department/SIRET into a coherent 'area' concept, but it never mentions decalage (presumably an offset for pagination), lots_min as a filter, or type_syndic, leaving three parameters with no meaning anywhere.

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 resource and condition: French condominiums whose syndic mandate ends soon, retrieved by area. It is far more specific than the name alone, but it never distinguishes itself from the sibling syndic_lookup, so an agent must infer which one to pick when both could plausibly match.

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 through the listed lookup keys (commune, postal code, department, SIRET) and the audience note ('Prospect list for property managers, insurers, contractors'), which hints at the prospecting scenario. There is no explicit when-not guidance and no mention of syndic_lookup as an alternative for a different need.

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

All Sentinelle syndic FR 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.