Skip to main content
Glama

Get property

get_property
Read-onlyIdempotent

Get a single property by its Straply ID (an opaque string like 'stp_x7Kd9Qm2Rb', as returned by search_properties). Returns the full property record including address, price, beds/baths, square footage, year built, lot size, property type, listing status, price history (all listing/sale/price-change events), and tax history.

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": {
      "property_id": "<property_id>"
    },
    "name": "get_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYesStraply property ID (e.g. 'stp_x7Kd9Qm2Rb')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 covered. The description adds genuinely useful behavior beyond that by spelling out the response payload — full record with price history and tax history — which matters because no output schema exists. It omits error/not-found behavior for an opaque ID, which is the main remaining gap.

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?

Two sentences, front-loaded with the operation and identifier, then the payload. The long field list is justified because there is no output schema to describe return values, so every field named serves a purpose.

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-parameter, annotation-covered lookup with no output schema, the definition covers what goes in and what comes back, which is the bulk of what an agent needs. It stops short of stating failure behavior for an invalid or unknown ID, leaving that to be discovered at call time.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by characterizing the ID as an opaque string — telling the agent not to parse or construct it — plus its provenance from search_properties. This adds meaning beyond the schema's bare 'Straply property ID' with an example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a single property'), names the identifier type, and enumerates the record contents. It also ties the ID to search_properties, which distinguishes it from sibling search/list tools without needing either schema.

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

Usage Guidelines4/5

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

Gives clear context: this is the single-record fetch and the ID comes from search_properties, so the agent knows the prerequisite step. It does not explicitly address the case where the agent only has an address (lookup_property_by_address) or otherwise lacks an ID, so exclusion guidance is incomplete but the positive path is unambiguous.

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