Skip to main content
Glama

NorthEast Deal Intel

Listing cap rate benchmarks

get_market_benchmarks
Read-onlyIdempotent

Get average, minimum and maximum asking cap rates from NDI listing data, by state and property type.

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

Input Schema

NameRequiredDescriptionDefault
stateNoCT
property_typeNo

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine behavioral context by naming the data source (NDI listings) and the aggregate shape returned (average/min/max). It does not disclose how an empty property_type default behaves or whether results are scoped to active listings only.

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 resource and its scope come first. It is tight, though it spends nothing on routing or default behavior, which the low guidance scores reflect rather than this dimension.

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 two-parameter, zero-required read tool with full safety annotations and no output schema, the description covers source, aggregation and grouping adequately. The one meaningful gap is the undocumented semantics of the empty property_type default, which is minor for a lookup of this simplicity.

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 description coverage is 0%, so the description must carry the parameter burden, and it does map both parameters to their meaning ('by state and property type'). However, it never explains what the empty-string default for property_type selects, nor what valid state values look like, so the most consequential ambiguity in the schema is unresolved.

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 names a specific verb ('Get'), a precise resource ('average, minimum and maximum asking cap rates'), a data source ('NDI listing data'), and the grouping dimensions ('by state and property type'). An agent can distinguish this from get_market_summary or score_deal without opening the schema, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as get_market_summary. Usage is only inferable from the phrase 'benchmarks' and the topic, leaving the agent to guess at the intended decision context.

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