Skip to main content
Glama

Get regional indicators

get_indicators
Read-only

Cited regional statistics for Finger Lakes and Southern Tier counties (Steuben, Yates, Schuyler, Ontario, Seneca) and for Hornell, Canisteo, Hammondsport, Bath, Penn Yan, Corning, Watkins Glen, Geneva and Canandaigua: ACS population, income, housing, rent and broadband subscription; NYS DOL LAUS unemployment (counties); NYSED school enrollment (municipal districts); and Tourism Economics / ESD visitor and lodging spending (counties). Every figure includes a source URL and a checked date. This is an independent compilation, not an official government dataset.

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

Input Schema

NameRequiredDescriptionDefault
geoNoCounty or municipality name or slug, e.g. "Steuben County", "hornell"
kindNocounty or place
indicatorNoOptional series id, e.g. unemployment_rate, median_gross_rent, visitor_spending, school_enrollment_k12, broadband_subscription_share, population, median_household_income

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with a static read-only compilation. It adds genuinely useful context beyond the annotations: every figure carries a source URL and checked date, the specific upstream datasets (ACS, NYS DOL LAUS, NYSED, Tourism Economics/ESD) and their geographic grain, and the caveat that this is an independent compilation rather than an official government dataset.

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?

Front-loaded with the resource and coverage area, then provenance, then the citation guarantee and the independence caveat. The place-name enumeration is long but each clause adds discriminative information an agent needs to decide whether its target geography is supported.

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 three-optional-parameter read tool with no output schema, the description supplies coverage, provenance, and the shape of returned values (figure plus source URL and checked date). The remaining gap is behavior when all parameters are omitted and any paging or result-size expectations.

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 baseline is 3, but the description goes beyond it by tying indicator families to geography types (LAUS unemployment and tourism spending at county level, school enrollment at municipal district level), which tells the agent which kind/geo combinations are coherent. It still does not explain slug normalization or what happens when indicator is omitted.

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 names a specific resource (cited regional statistics) and enumerates the exact geography (Finger Lakes/Southern Tier counties plus nine municipalities) and indicator families it covers. An agent can tell it returns sourced statistical figures rather than place descriptions. It stops short of naming a sibling to differentiate from, and there is no leading verb naming the retrieval action.

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: the geography and indicator list signals 'call this when you need a number with a citation for these places.' There is no explicit when-to-use versus when-not, and no mention of how it relates to the place/town/conditions siblings.

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.

Resources