Skip to main content
Glama

Realtors Dashboard

Florida recorded-sale market profile

get_florida_sales_profile
Read-onlyIdempotent

Get statewide or county sale price quartiles, property-type and month breakdowns, and the published county ZIP and city breakdowns. Price statistics require at least 10 records.

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

Input Schema

NameRequiredDescriptionDefault
countyNoFlorida county slug, for example miami-dade

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered without description help. The description adds a genuinely useful behavioral fact beyond annotations: price statistics are suppressed below 10 records. It says nothing about return shape, ordering, or how partial-coverage counties behave, which keeps this at a 3.

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 output inventory, and the threshold caveat placed last where it belongs. The enumerated breakdown list is dense but each item maps to a distinct output component, with no filler wording.

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 single optional-parameter read tool with rich annotations and no output schema, the description covers what is produced, the scope switch, and the minimum-record rule. The main residual gap is that it does not tell the agent when this profile is preferable to the raw-search sibling.

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?

With one optional parameter and 100% schema description coverage, the schema already documents the county slug format and example. The description only implies the omitted-county default via 'statewide or county' and adds no format, casing, or resolution details beyond the schema, so baseline 3 applies.

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 uses a specific verb-and-resource framing: it returns sale price quartiles, property-type and month breakdowns, and the county ZIP and city breakdowns for Florida, with statewide vs county scope stated. It is clearly an aggregate/market-profile tool, though it never names a sibling to distinguish itself from search_florida_recorded_sales or get_housing_market.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The only conditional statement is a data-threshold rule ('Price statistics require at least 10 records'), which is a constraint rather than routing guidance, so an agent must infer that this tool is for aggregates while search_florida_recorded_sales is for raw records.

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.