Skip to main content
Glama

Find owners

spur_find_owners
Read-onlyIdempotent

Find property owners in the user's Spur account by name, phone, email or mailing address text. Use spur_get_owner for full details and portfolio.

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": "spur_find_owners"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return
queryNoText to match against name, email, phone or mailing address
offsetNoNumber of items to skip, for pagination
has_dncNoOwners with a blocked DNC/TCPA phone
has_emailNo
has_phoneNoOnly owners with at least one phone number
max_propertiesNo
min_propertiesNo
enrichment_statusNoOnly owners with this skip-trace status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / has_dnc
      Added value: +{
      +  "description": "Owners with a blocked DNC/TCPA phone",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / has_email
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / max_properties
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / min_properties
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.9/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 only adds the account scope ('in the user's Spur account') and nothing about result limits, default page size, or how filters combine. Useful but thin against a lower bar.

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 short sentences, both earning their place: the searchable fields first, the sibling routing second. No filler or redundant restatement of the name.

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

Completeness3/5

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

For a nine-parameter search tool with no output schema, the description covers the text query but leaves the filtering and pagination surface unexplained. An agent would need to read the schema to discover that it can filter by DNC status, property count, or enrichment status, which is a meaningful completeness gap.

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 67%, so the schema documents most parameters already; the description only restates what the query parameter matches. It says nothing about the filter parameters (has_dnc, has_email, has_phone, min/max_properties, enrichment_status) or pagination behavior via limit/offset, so it adds no meaning beyond the schema.

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?

The description names a specific verb and resource ('Find property owners') and enumerates the searchable fields (name, phone, email, mailing address text). It also explicitly distinguishes itself from spur_get_owner, so an agent can tell the search tool from the detail tool without opening 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?

It states the lookup use case and names the alternative ('Use spur_get_owner for full details and portfolio'), which is a clear routing rule. It stops short of explicit when-not conditions, such as what to do if no owner matches or how to page through large result sets.

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