mcp.xynaptic

property-price

Xynaptic Property Price — official median price per sqm for a French commune and property type, computed from real transactions (DVF): median, mean, min/max, volume. GET ?city=Paris&type=Appartement. Robust median. Usage: Use for French real-estate price benchmarks by city and type (official DVF registry). Rents, valuations and yields are available through the xynaptic-catalog tool. [price: $0.020 per call, x402/USDC]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026
- changedInput schema / properties / params / properties / city / description
```
Previous value: -"example: \"Paris\""New value: +"required. example: \"Paris\""
```
- addedInput schema / properties / params / required
```
Added value: +[
+  "city"
+]
```
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "params"
+]
```

Changed4 schema fields changedOct 2, 2026

removedInput schema / properties / body

Removed value: -{
-  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
-  "type": "object"
-}

changedInput schema / properties / params / description

Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"

addedInput schema / properties / params / properties

Added value: +{
+  "city": {
+    "description": "example: \"Paris\"",
+    "type": "string"
+  },
+  "median_price_m2": {
+    "description": "example: 9538",
+    "type": "number"
+  },
+  "type": {
+    "description": "example: \"Appartement\"",
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[]
```

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the data source (official DVF registry), the return statistics (median, mean, min/max, volume), and the commercial/behavioural facts an agent must know before calling — $0.020 per call via x402/USDC. It does not cover error behaviour, coverage gaps for small communes, or latency.

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 scope, then example, then usage routing, then price. Every element is relevant, though "Robust median" is redundant with the earlier list of statistics and the description is dense enough that it reads as a tagline stack rather than prose.

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?

There is no output schema, so the description usefully enumerates what comes back (median, mean, min/max, volume) and identifies the upstream registry, plus cost and payment mechanism. For a single-parameter query tool this is close to sufficient; only error and coverage caveats are missing.

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 100%, so the schema already documents city (required) and type, making the baseline 3 appropriate. The description adds a concrete example call (GET ?city=Paris&type=Appartement), but it does not resolve the oddity that median_price_m2 is exposed as an input property when it reads like a response field, nor does it explain that type is optional.

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 resource (median price per sqm), a precise scope (French commune + property type), and the data provenance (real DVF transactions). It is clearly distinguishable from siblings like crypto-price, commodity-price, energy-price and security-price because the asset class is named up front.

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?

"Use for French real-estate price benchmarks by city and type" gives clear intended context, and it routes the agent to xynaptic-catalog for rents, valuations and yields. It stops short of an explicit when-not-to-use rule for this capability, but the domain boundary is unambiguous.

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

All mcp.xynaptic tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?