Skip to main content
Glama

NorthEast Deal Intel

State market summary

get_market_summary
Read-onlyIdempotent

Get a market summary for a state: active listing count, average asking cap rate, and top submarkets by listing count.

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

Input Schema

NameRequiredDescriptionDefault
stateNoCT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 the concrete return fields, which matters because there is no output schema. It omits data freshness, behavior on an unrecognized state value, and any scoping constraints.

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?

A single front-loaded sentence with no filler; the output fields are listed compactly after the core purpose. Nothing is redundant, though the terseness leaves obvious gaps addressed in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, closed-world read tool with full safety annotations, the description covers purpose and the shape of the return value. The remaining omission, the default state value, is a minor detail relative to the tool's simplicity.

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

Parameters2/5

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

There is one parameter with 0% schema description coverage, and the description contributes only the phrase 'for a state', which merely restates the parameter name. It never states the expected format (two-letter code vs. full name) or that the default is CT, both of which an agent needs to call it correctly.

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?

Specific verb (get) plus resource (market summary) and an explicit enumeration of the returned metrics: active listing count, average asking cap rate, top submarkets. An agent knows exactly what comes back. It does not, however, distinguish itself from sibling get_market_benchmarks, which is likely the closest alternative.

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 provided, and no alternative is named. The agent must infer from the sibling name alone whether get_market_benchmarks or this tool is the right call for a given question.

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