Skip to main content
Glama
Sign In

Should I Live Here?

by io.github.gdtilghman
OverviewDiscussionsAdmin

rank_counties

Read-onlyIdempotent

Rank counties in the lower 48 states on weighted measures, with the same scoring as the site's My priorities. Rank 1 has the lowest concern score. Counties with missing data are left out, never scored as low. Optional limits and state filter. Read the cautions in every answer.

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": {
      "measures": "<measures>"
    },
    "name": "rank_counties"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many counties to return. Default 10.
stateNoState name, postal code or 2-digit FIPS.
measuresYes
min_populationNoLeave out counties with fewer residents than this (Census ACS 2019-2023). Small counties have unstable rates; 10000 or more is a common choice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low, and the description still adds real substance: missing-data counties are dropped rather than penalized, rank ordering direction is explicit, and answers carry cautions. It stops short of describing the shape of the returned ranking or how ties/weights interact.

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?

Tight and front-loaded: scope and ranking semantics come first, exclusions and filters follow. No sentence is wasted, though the trailing 'Read the cautions in every answer' is vague enough to read as filler unless the agent already knows what the cautions are.

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?

A four-parameter read tool with no output schema whose risky edge cases (missing data, ranking direction, filter limits) are all addressed. Only gap is that the returned payload's contents are never characterized, which matters for a ranking tool with no output schema.

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

Parameters3/5

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

Schema coverage is 75% and the schema already documents defaults, the max/min interaction rule, the measure key source and the population caveat. The description contributes only 'Optional limits and state filter,' which the schema states more precisely, so this sits at the baseline.

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 (rank counties) plus a hard geographic scope (lower 48 states) and a scoring model (same as the site's My priorities, rank 1 = lowest concern). That is far more than a restatement of the name, but it never names or contrasts the sibling it most overlaps with, compare_counties, so the agent must infer the split.

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?

The only usage steer is 'Optional limits and state filter,' which implies the schema's count/state/min/max levers but does not say when to pick this over compare_counties or get_county. 'Read the cautions in every answer' hints at an operational prerequisite without defining it.

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

All Should I Live Here? toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources