Skip to main content
Glama

Dyscalculia prevalence figures

get_prevalence
Read-only

Returns the published dyscalculia prevalence entries, one per population study or guideline: the figure or range in percent, sample size, publication year, stated age, a calc flag (true when the site calculated the figure itself) and the reference key with a short citation. Use this when you need a prevalence number and its source; use list_chart_data instead for the page's other datasets (persistence, sex ratio, comorbidity, maths anxiety, interventions, the by-country table), and get_reference or list_studies to look up sources rather than figures. Filters combine (all must match); with none, it returns all 10 entries in the page's order, not sorted by figure or year, together with count, the statistics page URL and its last-updated date. An unknown study id returns an error listing the valid ids, and min_pct above max_pct returns an error; the entry id is only a label in this dataset, so to cite a number cite its study via get_reference. These are published research estimates, not a diagnosis of any person. There is no worldwide pooled meta-analysis of dyscalculia prevalence: the 'worldwide' entry is a range across population studies. Studies use different criteria and ages, so figures are not directly comparable.

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

Input Schema

NameRequiredDescriptionDefault
ageNoAge in whole years, 3 to 99, e.g. 11. Keeps entries whose stated age range includes it. Entries with no numeric age range are never matched; their ids are returned in notMatchedBecauseNoStatedAge.
studyNoExact entry id (case-sensitive); returns only that entry. One of: worldwide-range, german-guideline, israel-1996, brazil-2016, uk-morsanyi-2018, england-devine-2018, england-devine-2013, uk-lewis-1994, flanders-2004, inserm-2007. Omit for all entries.
max_pctNoUpper bound in percent, 0 to 100. Keeps entries whose figure, or the lower end of whose range, is at most this. Combine with min_pct for an overlap window.
min_pctNoLower bound in percent, 0 to 100. Keeps entries whose figure, or the upper end of whose range, is at least this. Combine with max_pct for an overlap window; must not exceed max_pct.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / age / description
      Previous value: -"Age in years, e.g. 11."New value: +"Age in whole years, 3 to 99, e.g. 11. Keeps entries whose stated age range includes it. Entries with no numeric age range are never matched; their ids are returned in notMatchedBecauseNoStatedAge."
    • changedInput schema / properties / max_pct / description
      Previous value: -"Upper bound in percent."New value: +"Upper bound in percent, 0 to 100. Keeps entries whose figure, or the lower end of whose range, is at most this. Combine with min_pct for an overlap window."
    • changedInput schema / properties / min_pct / description
      Previous value: -"Lower bound in percent."New value: +"Lower bound in percent, 0 to 100. Keeps entries whose figure, or the upper end of whose range, is at least this. Combine with max_pct for an overlap window; must not exceed max_pct."
    • changedInput schema / properties / study / description
      Previous value: -"One study id: worldwide-range, german-guideline, israel-1996, brazil-2016, uk-morsanyi-2018, england-devine-2018, england-devine-2013, uk-lewis-1994, flanders-2004, inserm-2007."New value: +"Exact entry id (case-sensitive); returns only that entry. One of: worldwide-range, german-guideline, israel-1996, brazil-2016, uk-morsanyi-2018, england-devine-2018, england-devine-2013, uk-lewis-1994, flanders-2004, inserm-2007. Omit for all entries."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses default ordering (page order, not sorted by figure or year), the exact entry count (10), the count/stats-page-URL/last-updated metadata, and two explicit error behaviours (unknown study id, min_pct > max_pct). It also flags interpretive limits: figures are not directly comparable, no pooled meta-analysis exists, and this is not a diagnosis.

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?

Purpose and the sibling routing come first, then return shape, then failure modes, then caveats — a sensible front-loaded order with no filler sentences. It is nonetheless a dense paragraph carrying several caveats (worldwide range, comparability, non-diagnosis) that could be tightened, which keeps it off a 5.

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 compensates by naming every returned field and the envelope metadata, and it covers ordering, empty-filter behaviour, error paths, and interpretive caveats. There is nothing an agent needs in order to call this correctly that is missing.

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 cross-parameter semantics the schema never states, namely that filters combine conjunctively ("all must match"). It also reinforces the error case for an inverted pct window and clarifies that the study id is only a dataset label. It does not add format detail beyond the schema, so it stops short of a 5.

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?

Opens with a concrete verb and resource ("Returns the published dyscalculia prevalence entries") and immediately enumerates the returned fields and granularity (one per population study or guideline). It explicitly distinguishes itself from list_chart_data, get_reference and list_studies, so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ("when you need a prevalence number and its source") plus named alternatives for the neighbouring needs: list_chart_data for other page datasets, get_reference/list_studies for sources rather than figures. It also states the no-filter default and the constraint that entry ids are labels, not citable sources.

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.