Skip to main content
Glama

New development details

get_development
Read-onlyIdempotent

Use this for one new development: its builder, homes for sale, reserved and coming soon with prices, the house types and their prices, the offers stated, homes that have left with their last prices, and the builder's own words from its brochure and site when asked (query). Name it by the page address a search returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "development": "<development>"
    },
    "name": "get_development"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to find in the builder's brochure, floor plans and descriptions: 'study', 'EV charger'.
developmentYesThe page address a search returned (ref), or the full link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower, and the description still adds real value: it discloses the return surface, including that sold homes are reported with last prices and that brochure/description text appears only when query is supplied. That conditional-output behavior is exactly the kind of trait annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single run-on sentence carrying seven clauses separated by commas, with the parameter hint buried in a parenthetical ('when asked (query)'). Every clause is informative — no padding — but the lack of sentence breaks and the placement of the query guidance after a long enumeration hurts scanability.

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?

There is no output schema, so the description must carry the return contract, and it does so thoroughly (builder, listings, staged inventory, pricing, offers, withdrawn homes, brochure text). With only two fully-described parameters and a complete read-only annotation set, an agent has enough to call this correctly.

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 100%, so the baseline is 3: the schema already explains that development is 'the page address a search returned (ref), or the full link' and that query is words to find in brochure/floor plans. The description only restates the identifier rule and adds a light 'when asked' framing for query, which is a marginal gain over structured data.

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+resource ('Use this for one new development') and enumerates what it returns: builder, homes for sale, reserved/coming soon with prices, house types, offers, departed homes, brochure text. It also routes implicitly by saying to identify the development by 'the page address a search returned', which distinguishes it from a search tool. It never names a sibling directly, so the differentiation is inferential rather than explicit.

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?

It says when to use it ('for one new development') and gives a usable condition for the optional query parameter ('the builder's own words... when asked'). But there is no statement of when NOT to use it, no mention of get_home vs. get_development, and no prerequisite such as 'call search_developments first to obtain the page address'.

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