Tulina

foncier_comparables_app

Rendered transactions around an address (MCP App / interactive table), DVF+.

Visual flagship variant of foncier_comparables_adresse: geocodes the address, then renders the local median €/m² plus a sortable/searchable table of nearby DVF+ mutations (date, address, type, surface, price, €/m², distance — all property types). Use when the user wants to see nearby sales. For raw JSON use foncier_comparables_adresse.

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": {
      "adresse": "<adresse>"
    },
    "name": "foncier_comparables_app"
  }
}

Input Schema

Name	Required	Description
`_org`	No	Org (id) de CET APPEL. `oto_list_orgs()`.
`limit`	No	max comparables, nearest first (default 50).
`years`	No	lookback in years with data (default 3).
`_group`	No	Équipe (id) de CET APPEL, sous son org parente.
`_run_id`	No	OBLIGATOIRE à 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.
`adresse`	Yes	free-form address (e.g. "44 la canebière marseille").
`_project`	No	Projet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
`radius_m`	No	search radius in metres (default 500).
`_instance`	No	Instance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
`type_local`	No	"Appartement" \| "Maison" (default: both).
`surface_max`	No
`surface_min`	No

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the critical behavioral trait: the output is a rendered MCP App / interactive table, not machine-readable JSON, and the address is geocoded internally before the search. It also enumerates the returned columns and the median €/m², which tells the agent what it will get. It stops short of covering failure modes (e.g. address that cannot be geocoded) or the auth/org context requirements handled by the schema.

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 purpose and the differentiator, then the fields, then the usage rule — a sensible order. The parenthetical field enumeration is long but informative rather than filler; only the 'DVF+ / MCP App' jargon opening costs a point.

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 12-parameter tool with no output schema, the description effectively documents the return shape (median €/m² plus a table of date, address, type, surface, price, €/m², distance) and the internal geocode step. That is enough for an agent to call it correctly; only edge-case behavior and pagination are unaddressed.

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 high (83%) and every parameter except surface_min/surface_max already carries a description, so the schema does the heavy lifting. The description only adds the semantic note that the table spans 'all property types' while type_local defaults to both. Baseline 3 is appropriate.

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 — renders DVF+ real-estate transactions around an address — and immediately names its relation to the sibling foncier_comparables_adresse as the visual flagship variant. An agent can distinguish it from the raw-JSON variant without opening 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 Guidelines5/5

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

Explicit selection rule: 'Use when the user wants to *see* nearby sales' and 'For raw JSON use foncier_comparables_adresse.' This gives both when-to-use and the concrete alternative that selects the sibling.

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

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