Skip to main content
Glama

Swapwire

Get license statistics by county and trade

get_area_stats
Read-onlyIdempotent

Counts for each county and trade in the dataset: licenses, how many carry workers' comp insurance or are exempt, how many have a suspension code, median years licensed and how many were issued in the last two years. Useful for saying whether one contractor's record is typical.

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

Input Schema

NameRequiredDescriptionDefault
tradeNoOptional trade filter.
countyNoOptional county filter.

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, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful non-annotation context: the result is grouped aggregates over the dataset rather than per-license rows, and it spells out exactly which measures are computed (insurance/exempt counts, suspension codes, median years licensed, recent issuances). It does not describe the result shape or ordering, which keeps it from a 5.

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?

Two sentences, front-loaded with the grouping vocabulary and then the metric list; every clause adds a distinct measure rather than restating the title. The long enumeration is dense but each item earns its place by telling the agent what columns to expect.

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?

With no output schema, the description is the only source of return-value information and it does discharge that duty by naming the computed measures. For a simple two-optional-filter read tool this is largely sufficient, though it leaves open what happens with no filters and what the 'dataset' scope actually is (the enums suggest a limited county/trade set).

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 100% with enums and 'Optional' descriptions on both parameters, so the schema carries the parameter semantics. The phrase 'for each county and trade' hints that these are the grouping dimensions rather than only filters, which adds a little meaning, but it does not clarify the behavior when a filter is omitted (aggregate across all counties/trades?) beyond what the schema states.

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 opens with a concrete verb and resource ('Counts for each county and trade in the dataset') and then enumerates the exact metrics computed, so an agent knows this is an aggregate/benchmarking tool rather than a record lookup. It is clear but never names a sibling to contrast with, so differentiation from get_license or search_licenses is left to inference.

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 closing sentence 'Useful for saying whether one contractor's record is typical' gives an implied use case (benchmarking against peers), which is more than nothing. However, there is no explicit when-to-use/when-not guidance and no mention of the alternative tools an agent should pick when it wants a single record instead of aggregates.

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