Skip to main content
Glama

Realtors Dashboard

Florida recorded-sale coverage

list_florida_counties
Read-onlyIdempotent

List the active release, property counts and latest recorded-sale month for all 67 Florida counties.

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": "list_florida_counties"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds that results include the active release and latest recorded-sale month, i.e. a metadata snapshot rather than transaction records, but says nothing about ordering, size, or whether the county set can change between releases.

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?

One sentence, no filler, front-loaded with the verb and the full scope; every clause (release, counts, latest month) carries information an agent needs to decide whether the result is useful.

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 input parameters and no output schema, the description must convey the return shape, which it does at a high level (release version, per-county property counts, latest month). Only finer details — whether counties are returned as a keyed map or array, and how often the release updates — are left unspecified, which is acceptable for a simple enumeration tool.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies a no-argument, list-everything call with fixed scope of 67 counties, adding the only semantic that matters here.

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?

A specific verb ('List') plus resource ('Florida counties') and explicit scope ('all 67'), with the returned content named: active release, property counts, latest recorded-sale month. It is clearly distinguishable from recording-level siblings like search_florida_recorded_sales, though the description never names that alternative outright.

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: an agent can infer this is a coverage/overview call to make before drilling into recorded sales, but the description states no when-to-use condition, no prerequisites, and no comparison against search_florida_recorded_sales or get_florida_sales_profile.

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.