DeepPVMapper

aggregate_detection_capacity

Compute the total estimated installed capacity (kWp) and count of detections matching a set of filters — département, commune, capacity range, and cross-validation across sources (cross_validated) or imagery vintages (min_vintages) — plus a quality_summary for the summed sample. Unlike get_department_capacity_stats, which is a fixed pre-computed département-wide aggregate with no other filters, this tool sums a live filtered subset, up to max_rows detections. Example: "installed capacity in Gironde confirmed by at least two sources" -> dpt="33", cross_validated=true. Data quality note: this is a detection dataset, not an exhaustive inventory (estimated recall ~0.6). A missing detection does not mean no PV installation exists there. kwp, surface, tilt and azimuth are model estimates, not surveyed values. In this server, quality_filter=true keeps only detections identified by 2 or more sources (see source_encoding in get_data_quality_reference). Call get_data_quality_reference for the full picture before assessing fitness for a specific use case.

Input Schema

Name	Required	Description
`dpt`	No	French département code, e.g. "33".
`insee`	No	INSEE commune code.
`max_kwp`	No	Maximum estimated installed capacity, in kWp.
`min_kwp`	No	Minimum estimated installed capacity, in kWp.
`max_rows`	Yes	Cap on the number of matching detection rows fetched to compute the capacity sum. If the true match count exceeds this, total_kwp is a partial lower bound and `truncated` is true — increase max_rows or narrow the filters (e.g. add dpt or insee) for an exact total.
`max_tilt`	No	Maximum estimated tilt from horizontal, in degrees.
`min_tilt`	No	Minimum estimated tilt from horizontal, in degrees.
`has_rnb_id`	No	true = only detections matched to an RNB building identifier (rnb_id not null); false = only detections without one.
`max_azimuth`	No	Maximum estimated azimuth, degrees clockwise from true north (180 = south).
`max_surface`	No	Maximum estimated PV array area, in m².
`min_azimuth`	No	Minimum estimated azimuth, degrees clockwise from true north (180 = south).
`min_surface`	No	Minimum estimated PV array area, in m².
`max_vintages`	No	Maximum number of imagery vintages (e.g. 1 = seen in a single year only).
`min_vintages`	No	Minimum number of distinct imagery vintages (years) the installation was independently detected in. Use 2+ as a persistence/confidence signal, since a one-off detection in a single vintage is more likely to be a transient artifact.
`max_last_seen`	No	Upper bound on last_seen imagery year.
`min_last_seen`	No	Lower bound on last_seen imagery year.
`has_frpv_proba`	No	true = only detections that have an FRPV comparison (frpv_proba not null); false = only those without one. A null frpv_proba means "no comparison available", not probability 0.
`max_first_seen`	No	Upper bound on first_seen imagery year.
`min_first_seen`	No	Earliest imagery year of first detection, lower bound (e.g. 2018). Not an installation date.
`min_frpv_proba`	No	Minimum frpv_proba. The data contract recommends 0.1 as a precision/recall trade-off. Note: detections with a null frpv_proba (no FRPV comparison available) are excluded when this is set; null does not mean probability 0.
`quality_filter`	Yes	If true, only include detections identified by 2 OR MORE sources(the `sources` field lists at least two codes, e.g. "0,1" = DeepPVMapper pipeline + FRPV reference, "0,2" = pipeline + OpenStreetMap). Default false: all detections are included, including those found by a single source (typically the automated pipeline alone).
`cross_validated`	No	Alias of quality_filter, kept for backward compatibility.
`sources_include`	No	Only include detections present in ALL of these sources. Accepts names or codes, case-insensitive: dpvm/deeppvmapper/kasmi (0), frpv/thebault (1), osm/openstreetmap (2), manual/annotation (3), recall (4). Examples: ["osm"] = detections that are in OpenStreetMap; ["dpvm","frpv"] = present in both DeepPVMapper and FRPV. See get_source_reference for what each source is and where it comes from.
`false_positive_status`	No	flagged = false_positive is true; not_flagged = false_positive is false; unrecorded = false_positive is null (no status recorded — NOT a confirmed true positive).

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 18, 2026

changedInput schema / properties / cross_validated / description

Previous value: -"If true, only include detections confirmed by at least two independent sources (e.g. the automated DeepPVMapper pipeline plus OpenStreetMap or the FRPV reference dataset), not just a single pipeline. This is a stronger confidence signal than min_vintages."New value: +"Alias of quality_filter, kept for backward compatibility."

addedInput schema / properties / false_positive_status

Added value: +{
+  "description": "flagged = false_positive is true; not_flagged = false_positive is false; unrecorded = false_positive is null (no status recorded — NOT a confirmed true positive).",
+  "enum": [
+    "flagged",
+    "not_flagged",
+    "unrecorded"
+  ],
+  "type": "string"
+}

addedInput schema / properties / has_frpv_proba

Added value: +{
+  "description": "true = only detections that have an FRPV comparison (frpv_proba not null); false = only those without one. A null frpv_proba means \"no comparison available\", not probability 0.",
+  "type": "boolean"
+}

addedInput schema / properties / has_rnb_id

Added value: +{
+  "description": "true = only detections matched to an RNB building identifier (rnb_id not null); false = only detections without one.",
+  "type": "boolean"
+}

addedInput schema / properties / max_azimuth

Added value: +{
+  "description": "Maximum estimated azimuth, degrees clockwise from true north (180 = south).",
+  "type": "number"
+}

addedInput schema / properties / max_first_seen

Added value: +{
+  "description": "Upper bound on first_seen imagery year.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / max_last_seen

Added value: +{
+  "description": "Upper bound on last_seen imagery year.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / max_surface

Added value: +{
+  "description": "Maximum estimated PV array area, in m².",
+  "type": "number"
+}

addedInput schema / properties / max_tilt

Added value: +{
+  "description": "Maximum estimated tilt from horizontal, in degrees.",
+  "type": "number"
+}

addedInput schema / properties / max_vintages

Added value: +{
+  "description": "Maximum number of imagery vintages (e.g. 1 = seen in a single year only).",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / min_azimuth

Added value: +{
+  "description": "Minimum estimated azimuth, degrees clockwise from true north (180 = south).",
+  "type": "number"
+}

addedInput schema / properties / min_first_seen

Added value: +{
+  "description": "Earliest imagery year of first detection, lower bound (e.g. 2018). Not an installation date.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / min_frpv_proba

Added value: +{
+  "description": "Minimum frpv_proba. The data contract recommends 0.1 as a precision/recall trade-off. Note: detections with a null frpv_proba (no FRPV comparison available) are excluded when this is set; null does not mean probability 0.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / min_last_seen

Added value: +{
+  "description": "Lower bound on last_seen imagery year.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / min_surface

Added value: +{
+  "description": "Minimum estimated PV array area, in m².",
+  "type": "number"
+}

addedInput schema / properties / min_tilt

Added value: +{
+  "description": "Minimum estimated tilt from horizontal, in degrees.",
+  "type": "number"
+}

changedInput schema / properties / quality_filter / default
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / quality_filter / description

Previous value: -"If true (default), only include detections with frpv_proba >= 0.1, the threshold recommended in the data contract for a good precision/recall trade-off."New value: +"If true, only include detections identified by 2 OR MORE sources(the `sources` field lists at least two codes, e.g. \"0,1\" = DeepPVMapper pipeline + FRPV reference, \"0,2\" = pipeline + OpenStreetMap). Default false: all detections are included, including those found by a single source (typically the automated pipeline alone)."

addedInput schema / properties / sources_include

Added value: +{
+  "description": "Only include detections present in ALL of these sources. Accepts names or codes, case-insensitive: dpvm/deeppvmapper/kasmi (0), frpv/thebault (1), osm/openstreetmap (2), manual/annotation (3), recall (4). Examples: [\"osm\"] = detections that are in OpenStreetMap; [\"dpvm\",\"frpv\"] = present in both DeepPVMapper and FRPV. See get_source_reference for what each source is and where it comes from.",
+  "items": {
+    "anyOf": [
+      {
+        "maximum": 4,
+        "minimum": 0,
+        "type": "integer"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  "type": "array"
+}

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose substantive behavior: the dataset is a detection dataset with ~0.6 recall rather than an exhaustive inventory, missing detections do not imply absence of PV, and kwp/surface/tilt/azimuth are model estimates. It also surfaces the max_rows truncation caveat (partial lower bound) and that cross_validated is an alias of quality_filter. It stops short of cost/latency or permissions context, so not a 5.

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 core purpose and the sibling contrast before moving to example, data-quality caveats, and the reference pointer. It is on the long side and partially repeats what the schema already says (quality_filter semantics, cross_validated alias, truncation), which costs it a point, but each sentence carries information.

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 24-parameter tool with no output schema and no annotations, the description supplies the essential caveats an agent needs: the detection-vs-inventory framing, recall figure, model-estimate status of key metrics, and the truncation/partial-total behavior. It is reasonably complete, with only minor gaps around result shape and the semantics of the quality_summary it mentions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by tying filters together into a worked example and clarifying in prose that quality_filter=true means 'identified by 2 or more sources' and that cross_validated is a backward-compat alias. It doesn't re-derive every one of the 24 parameters, which is appropriate given the schema already documents them.

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+resource (compute total estimated installed capacity and count of matching detections) and enumerates the filter dimensions that define the subset. It explicitly distinguishes itself from the sibling get_department_capacity_stats (fixed pre-computed aggregate, no filters) versus this tool's live filtered sum, so an agent can route between them without opening a 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?

Gives explicit when-to-use-vs-alternative guidance by contrasting with get_department_capacity_stats, supplies a concrete worked example ("installed capacity in Gironde confirmed by at least two sources" -> dpt="33", cross_validated=true), and names the prerequisite reference tool (get_data_quality_reference) for fitness assessment. Nothing is left to inference.

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

All DeepPVMapper 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.

aggregate_detection_capacity

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources