The Cracks Index

Biggest risers and fallers

top_movers

Read-onlyIdempotent

Return the biggest risers and fallers between the two latest snapshots.

Compares every area's composite score in the most recent snapshot
against the snapshot before it and returns the areas that improved most
(``improvers`` — score fell) and worsened most (``decliners`` — score
rose). Needs at least two snapshots; returns an explanatory empty
payload otherwise.

Read-only, area-level aggregates only, no personal data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`level`	No	Area level to rank movers within: 'country', 'nuts2' (EU regions) or 'gemeente' (Dutch municipalities). Defaults to 'country'.	country
`limit`	No	How many risers and how many fallers to return each (1-50, default 5).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description adds valuable behavior: it compares composite scores, defines improvers and decliners with a counterintuitive naming explanation (improvers' score fell, decliners' rose), and discloses the empty payload when data is insufficient. It also confirms read-only, area-level aggregates, and no personal data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the core purpose, and uses a clear structured format. Every sentence adds value, explaining mechanism, edge case, and data safety without fluff.

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 a simple two-parameter schema and an output schema present, the description covers the tool's behavior, edge cases (needing two snapshots), and data characteristics fully. It is complete for an agent to use confidently.

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?

The input schema covers both parameters with descriptions, providing 100% coverage. The tool description adds no extra parameter-level detail, so the baseline score of 3 is appropriate.

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 clearly states the tool returns the biggest risers and fallers between the two latest snapshots, using a specific verb and resource. It distinguishes itself from sibling tools by focusing on temporal comparison rather than static rankings or area details.

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?

The description gives clear context: use when you need top movers between snapshots, and notes the precondition of at least two snapshots. It does not explicitly name alternative tools, but the context is sufficient for an agent to decide when this tool is appropriate.

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

All The Cracks Index tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct query: rankings, country details, region details, comparisons, trends, correlations, methodology, and improvement guidance. Despite minor overlaps (e.g., country_fix and improvement_guidance), descriptions clearly differentiate them, so an agent can reliably select the correct tool.

Naming Consistency3/5

Tool names mix patterns: some start with verbs (compare_countries, get_cracks_index), others with nouns (area_statistics, country_detail, methodology). While readable and clear, the lack of a consistent verb_noun or noun_verb paradigm reduces predictability for an agent.

Tool Count5/5

With 13 tools covering the full spectrum of index queries—rankings, details, comparisons, trends, correlations, methodology, and improvement guidance—the count is well-scoped for the domain. No tool feels superfluous, and the set is neither too sparse nor too bloated.

Completeness5/5

The tool surface provides complete CRUD-like coverage for the Cracks Index: full ranking, per-area detail and breakdown, comparisons, trends, top movers, indicator correlations, ranking by indicator, methodology, and improvement guidance. No obvious gaps exist for common agent workflows.

Resources

Need Help?