Skip to main content
Glama
StatsMapped: Irish statistics (CSO, county & council data)

StatsMapped: Irish statistics (CSO, county & council data)

get_scene

Returns structured data to draw citable Irish housing charts or clips from quarterly permission/commencement/completion figures or county-vs-median yearly rows; nothing is rendered.

Instructions

Use when asked for a chart, still or short clip of a figure you can cite: returns the data to DRAW one scene, nothing rendered.

Two scenes exist. "ireland-builds" is Ireland's homes granted permission, with a commencement notice and completed, by quarter from 2018Q1. "county-in-motion" is one county against the county median, one row per year: pass county (for example county:cork; default county:dublin) and terms ("real" default, or "nominal"); vintage does not apply to it. For ireland-builds the licence DIFFERS BY STAGE (see licence.stages): a stage whose licence is unconfirmed or ShareAlike is withheld (its cells are absences, not zeros) and the licence line names its holder. You get rows, a table twin, alt text, notes, absences (a missing figure is a typed absence, never a zero), the licence block, scene_hash, a receipt and the canonical URL. YOU draw it, and the last frame must match the table. Print the scene_hash and the licence line in the first, middle and last frame, quote only numbers that are in rows, do not loop, and keep the "stages are not a cohort" note. purpose is "analytical" (default) or "promotional": a promotional use of a source whose licence forbids advertising is refused (licence_refused). vintage (ISO date) omitted = the current data; an earlier vintage is not stored and returns unknown_vintage. Example: get_scene(scene_id="ireland-builds").

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

Input Schema

NameRequiredDescriptionDefault
termsNoreal
countyNo
countryNoireland
purposeNoanalytical
vintageNo
scene_idNoireland-builds

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.6
    • addedInput schema / properties / county
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "County"
      +}
    • addedInput schema / properties / terms
      Added value: +{
      +  "default": "real",
      +  "title": "Terms",
      +  "type": "string"
      +}
  2. Addedv0.3.4

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses output contents, licence-stage withholding, typed absences, refusal behavior for promotional use, vintage errors, and drawing constraints including scene_hash and licence-line requirements.

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 front-loaded with the core use case and then organized by scene, licence, output, and drawing rules. It is dense but mostly earns its length, though there is some redundancy around absences and the non-rendered nature of the tool.

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?

For a complex six-parameter tool with no annotations and an output schema, the description is highly complete. It covers scene behavior, licence constraints, error cases, output fields, and agent drawing obligations, with only the country parameter omitted.

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 description coverage is 0%, so the description must compensate, and it explains scene_id, county, terms, purpose, and vintage with defaults and examples. However, the country parameter is never mentioned, leaving one of six parameters undocumented.

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 states a specific verb and resource: it returns data to draw one scene, not a rendered output. It clearly scopes the tool to chart/still/clip requests and names the two available scenes, but it does not explicitly differentiate itself from sibling tools such as query_data or compare.

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 when-to-use guidance: use when asked for a chart, still, or short clip of a citable figure. It also explains scene selection, purpose modes, and vintage behavior, but it does not name alternatives or state when not to use this tool.

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