Skip to main content
Glama

Attention to German parties (Wikipedia pageviews)

get_party_attention
Read-only

Free. Views of the Bundestag parties' German Wikipedia articles (Wikimedia Pageviews API, CC0, human readers): last full day vs the usual day (median of 28 days), ratio, surge flag at 2.5x, 7-day series and monthly views for about five years. This is attention, not support: not a forecast, not search queries, not an audience limited to Germany, no ranking, no seat or coalition projection. CDU and CSU are separate articles (polls combine them). Attribution is in the response. Refreshed every 3 hours.

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_party_attention"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond that — data provenance and CC0 licensing, human-reader filtering, a 3-hour refresh cadence, attribution present in the response, and the exact methodology (last full day vs 28-day median, 2.5x surge threshold). It also preempts misinterpretation by stating the signal is attention, not support or a forecast.

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 and dense with no filler; lead words 'Free.' and the source citation set expectations immediately. The caveat list is longer than strictly necessary and reads as one packed enumeration, but each clause carries disambiguating information.

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?

There is no output schema, so the description carries the return-value burden and does so: it enumerates the last-day figure, 28-day median baseline, ratio, 2.5x surge flag, 7-day series, and multi-year monthly views. Combined with the refresh cadence and attribution note, an agent has everything needed to call and interpret it without guessing.

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 takes no parameters, so per the baseline this scores 4. The description makes clear the call requires no input and that the returned figures (ratio, surge flag, 7-day series, ~5 years of monthly views) are fixed in shape.

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 and resource ('Views of the Bundestag parties' German Wikipedia articles'), names the data source (Wikimedia Pageviews API), and delimits scope (human readers, not an audience limited to Germany). It also distinguishes itself from the polls sibling by noting CDU and CSU are separate articles while polls combine them.

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?

Gives strong when-not guidance: 'not a forecast, not search queries, not an audience limited to Germany, no ranking, no seat or coalition projection,' which steers an agent away from using it as polling or election-projection data. It stops short of naming a concrete alternative tool and condition (e.g. 'for polling numbers use get_german_polls'), so the routing is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.