mcp-resilland

get_stats_overview

Get a live overview of platform performance: document counts, vector chunks, NDVI rasters, Sentinel scenes, data-source details, per-country coverage, and recent ingestion activity.

Instructions

Live platform KPIs straight from the production DB.

Returns 8 counters (documents, pgvector chunks, avg chunk tokens, NDVI rasters, Sentinel scenes, active data sources, total area hectares, cadastral parcels, nurseries, finalised reports), plus a data-sources panel, per-country coverage (UZB/KAZ/KGZ/TJK/TKM/ TUR), and a recent ingestion activity feed.

Same payload the resilland.com /stats dashboard renders.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions the production DB source and lists return contents, implying a read-only operation, but it does not explicitly state safety aspects, potential performance impact, or access requirements. It adds some context beyond a minimal description but lacks depth.

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 description is concise and well-structured, with a short opening sentence followed by a detailed but organized enumeration of return fields. The final sentence about the dashboard payload is slightly redundant with the opening 'Live platform KPIs' but doesn't waste much space. It earns a 4, not 5, due to minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, an output schema exists, and the description thoroughly enumerates all return sections (counters, data-sources panel, country coverage, activity feed), it is contextually complete. The description leaves no ambiguity about what the tool returns, and the output schema covers return values. A 5 is justified for this no-param tool.

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?

The tool has zero parameters, so the baseline score is 4 according to the rubric. The description adds no parameter details because none are needed; the schema's additionalProperties: false confirms there are no inputs. Thus a score of 4 is appropriate.

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?

The description clearly states the tool returns live platform KPIs and enumerates specific counters and panels, making the purpose obvious. However, it does not explicitly differentiate from the sibling tool get_stats_summary, which likely serves a similar function. A 5 would require explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus get_stats_summary or other siblings. The phrase 'straight from the production DB' implies a live read but offers no exclusions, prerequisites, or alternative recommendations. This is a clear gap for a tool with a closely named sibling.

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

Deploy Server