Skip to main content
Glama
ElectionData MCP

ElectionData MCP

find_seat_by_location

Read-only

Locate the Parliament and state seats containing a latitude and longitude, using boundary maps in force for a chosen year, with optional polling district detail.

Instructions

Find the Parliament and state seats (optionally polling district) that contain a point. Uses the boundary maps in force in the given year (now if not given).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "find_seat_by_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
yearNo
include_districtNo
include_proposedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: it resolves boundaries using the maps in force for the supplied year, defaulting to the current year, and returns multiple levels of geography. It does not explain what 'proposed' boundaries mean or how the district flag interacts with the returned polling district.

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?

Two dense sentences that get the result shape up front and the temporal scoping second. No filler, no restatement of the tool name.

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

Completeness3/5

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

An output schema exists, so return structure need not be described. However, for a five-parameter spatial lookup the description leaves include_proposed and the district option ambiguous, and gives no cue about relationship to the broader seat/search tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains lat/lon implicitly ('a point') and year explicitly ('boundary maps in force in the given year (now if not given)'), but 'optionally polling district' maps only loosely onto include_district, and include_proposed is never mentioned at all -- so roughly a third of the parameters remain unexplained in both schema and description.

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?

States a specific verb and resource: find the Parliament and state seats (optionally polling district) that contain a point. That is a precise point-in-polygon lookup, distinct from the demographic/history siblings. It stops short of naming any sibling to contrast against, so it is clear but not differentiating.

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

Usage Guidelines3/5

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

Usage is only implied by the input shape -- you supply lat/lon when you have a coordinate and want to know its seat. There is no statement of when to prefer this over a name-based lookup or a dataset/table tool, and no prerequisites or exclusions are given.

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