Skip to main content
Glama

get_scene

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 changed
    • 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. Added

TDQS

A4.4/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 burden and does so: it discloses that nothing is rendered, that licence status differs by stage and unconfirmed/ShareAlike stages are withheld as absences rather than zeros, that promotional use against an ad-forbidding licence is refused, and that a non-current vintage is not stored. It also gives caller obligations (print scene_hash and licence line in first/middle/last frame, quote only numbers in rows, keep the stages note), which is unusually rich for a no-annotation tool.

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

Conciseness3/5

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

Nearly every clause carries information, and the trigger is front-loaded, but the middle is a run-on tangle of parentheticals and mid-sentence line breaks that makes the licence/stage rules hard to parse on first read. A short structured list of scenes, parameters, and caller obligations would convey the same content with far less friction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations and no schema descriptions, the description is close to sufficient: scene selection, licence semantics, absences, refusal modes, and drawing obligations are all covered. The gaps are the undocumented `country` parameter and a partly redundant restatement of return fields that the output schema already covers.

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 supply meaning, and it defines five of six parameters well: `terms` (real default vs nominal), `county` (example syntax county:cork, default dublin), `vintage` (ISO date, omitted = current, plus that it does not apply to county-in-motion), `purpose` (analytical default, promotional refusal), and `scene_id` (two named values plus a call example). `country` is never mentioned and its effect is left entirely unexplained.

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 output: it returns the data needed to DRAW one scene and explicitly renders nothing, which separates it from any render/query sibling. It also enumerates the two available scenes by id with what each contains, so an agent knows exactly what it will get.

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?

Opens with an explicit trigger ('Use when asked for a chart, still or short clip of a figure you can cite') and adds conditions for `purpose` and `vintage`, including the licence_refused and unknown_vintage outcomes. It never names a sibling tool to use instead when no drawable scene fits, so the alternatives side of the guidance is missing.

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.