Skip to main content
Glama

PeppolStatus

by com.peppolstatus
OverviewDiscussionsAdmin

get_adoption

Read-only

Get a country's adoption aggregates

Peppol adoption for one country as one bare object: headline totals (universe, on_peppol, penetration), the single-dimension cuts (sector with a NACE section rollup, region, FR-only département + size class, BE-only province + postcode + mandate scope, legal-form family, and company age), the same categorical cuts cross-tabbed by company-age band (cuts_by_age), and the trend (monthly new adopters plus per-run penetration history). Region cells carry ISO 3166-2 (BE) / INSEE région (FR) codes and sector cells the NACE division code, so the choropleth joins geometry with no string matching. Numerator cells below 10 matched companies are suppressed (on_peppol/penetration null, suppressed true); denominators are never suppressed. Cached for a day (data moves monthly).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesCountry code — `be`, `fr`, `sk`, `no`, `se` or `fi`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code — `be`, `fr`, `sk`, `no` or `se`."New value: +"Country code — `be`, `fr`, `sk`, `no`, `se` or `fi`."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "be",
-  "fr",
-  "sk",
-  "no",
-  "se"
-]New value: +[
+  "be",
+  "fr",
+  "sk",
+  "no",
+  "se",
+  "fi"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code — `be`, `fr`, `sk` or `no`."New value: +"Country code — `be`, `fr`, `sk`, `no` or `se`."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "be",
-  "fr",
-  "sk",
-  "no"
-]New value: +[
+  "be",
+  "fr",
+  "sk",
+  "no",
+  "se"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code — `be` or `fr`."New value: +"Country code — `be`, `fr`, `sk` or `no`."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "be",
-  "fr"
-]New value: +[
+  "be",
+  "fr",
+  "sk",
+  "no"
+]
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=true, so the description carries the burden of explaining behavior. It discloses suppression rules (numerators below 10 suppressed, denominators never), caching (cached for a day with monthly data moves), and the structure of the response. This goes well beyond the minimal read-only hint and provides actionable transparency.

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 longer than average but front-loaded with the core purpose and then layered with dense, useful detail about cuts, codes, suppression, and caching. Each sentence adds value, though some phrasing is complex and could be tightened without losing info.

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?

With no output schema, the description must explain return values, and it does so thoroughly: list of headline fields, cuts and cross-tabs, coding schemes, suppression behavior, and caching. It also clarifies the data's geographic scope and update frequency. For a complex aggregate tool, this is complete.

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% and the country parameter is already described with an enum and explanation. The description adds no detail about the parameter beyond its role as the country selector; it does mention 'one country' but that is already evident from the schema. Baseline 3 applies.

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?

The description begins with a clear verb+resource: 'Get a country's adoption aggregates'. It enumerates the exact content: headline totals, cuts, cross-tabs, and trend, making the tool's purpose concrete and distinct from sibling tools like get_country_churn or get_summary.

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

Usage Guidelines3/5

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

Usage context is implied: this targets a single country's adoption aggregates, and the required 'country' parameter enforces that scope. However, the description does not explicitly mention when not to use it or name alternative tools (e.g., for multi-country or network-wide adoption), so the guidance is only implied.

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