Skip to main content
Glama

Look up property by address

lookup_property_by_address
Read-onlyIdempotent

Find a property by street address and ZIP code. Use this when you know the address but not the Straply ID. Returns the full property record.

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": {
      "street": "<street>",
      "zipCode": "<zipCode>"
    },
    "name": "lookup_property_by_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (optional, improves matching)
stateNoTwo-letter state code (optional)
streetYesStreet address (e.g. '1005 Benedict Canyon Dr')
zipCodeYesFive-digit ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The rich annotations (readOnly, idempotent, non-destructive, closed-world) already carry the safety profile, so the bar is lower. The description adds one genuine behavioral fact beyond them — "Returns the full property record" — which matters given there is no output schema. It says nothing about behavior on no match, multiple matches, or whether matching is exact or fuzzy.

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?

Three short sentences, front-loaded with the action, then the disambiguation rule, then the return. Nothing is redundant and nothing repeats the schema or annotations verbatim.

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 simple two-required-parameter lookup with full schema coverage and complete annotations, the description covers purpose, selection rule, and return shape. The remaining gap is the ambiguity path — what a caller should expect when the address matches nothing or matches several records — which would matter for an agent deciding whether to retry or follow up.

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 street, zipCode, city, and state are all documented in the schema, including the note that city improves matching. The description names the two required fields but adds no meaning beyond the schema, which is the expected baseline.

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 gives a specific verb and resource ("Find a property by street address and ZIP code") and implicitly distinguishes itself from an ID-based sibling by noting it is for when you lack the Straply ID. It stops short of naming the alternative tool, but the distinction is still actionable from the text alone.

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?

"Use this when you know the address but not the Straply ID" is explicit when-to-use guidance and implies the inverse case (you have an ID, use the other tool). No sibling is named outright and there is no statement about when this tool is a poor choice, such as ambiguous or partial addresses.

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