Skip to main content
Glama

PeppolStatus

by com.peppolstatus
OverviewDiscussionsAdmin

get_compliance_stats_history

Read-only

Network compliance trend

The network compliance picture over time: one point per UTC day the rollup ran, carrying that day's participant denominator, affected participants, error rate and open findings by grade. The series starts the day the rollup first ran. Keyless-cacheable.

Pass country for one country's trend (issue #716) — the same series shape, restricted to that country and echoed back in country. The per-country series starts the day the country rollup first ran, which is later than the network one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive upper bound (YYYY-MM-DD UTC). Defaults to today.
fromNoInclusive lower bound (YYYY-MM-DD UTC). Defaults to 90 days ago.
countryNoScope the trend to one ISO 3166-1 alpha-2 country (or `ZZ`). A country the rollup has not seen returns an empty series, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Scope the trend to one ISO 3166-1 alpha-2 country (or `ZZ`). A country the rollup has not seen returns an empty series, not an error.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint=true already covering safety, the description adds useful behavior: keyless cacheability, per-UTC-day rollup granularity, series-start semantics, and the country echo. It does not describe exact JSON field names, but the data content is sufficiently specified for a read-only history tool.

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 flows from headline to network-series details to country variant, with most sentences earning their place. Minor noise includes the 'issue #716' parenthetical and slight redundancy between the headline and the first sentence.

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 carries the return-value burden; it does so by stating point contents, series-start behavior, and country-scoping results. It could be more explicit about the exact response structure, but nothing essential is missing for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics for `country`—same series shape, echoed back, and a later series start—while to/from are already fully described by the schema.

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 identifies the resource (network compliance) and the temporal dimension ('one point per UTC day... over time'), making it easy to distinguish from a current-snapshot compliance endpoint. It lacks an explicit retrieval verb in the description itself, but the intent is unmistakable.

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?

It gives clear context for both invocation modes: omit `country` for the network trend or pass `country` for a single-country trend, including the later series-start date for country rollups. It does not explicitly contrast with `get_compliance_stats` or state when-not to use this tool, so it stops short of a 5.

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

All PeppolStatus toolsInspect
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