Skip to main content
Glama

Promise Land Appraisal public information

Search appraisal services

search_appraisal_services
Read-onlyIdempotent

Find residential appraisal services by matching a short, general question to published service names and descriptions. Do not include a property address, phone number, or email address.

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": {
      "query": "<query>"
    },
    "name": "search_appraisal_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesGeneral question about residential appraisal services. Do not include a property address, phone number, or email address.

Output Schema

NameRequiredDescriptionDefault
servicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds useful context beyond that: the search operates over published service names and descriptions, and PII must be excluded. It says nothing about result ranking, match behavior when nothing is found, or limits, which is why it does not rise above 3.

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?

Two short sentences, front-loaded with the purpose before the input constraint. Every clause carries information, though the PII sentence duplicates what the schema already documents for the parameter.

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?

A single required parameter, rich annotations, and an existing output schema mean the description need not explain return values. It covers purpose plus the main input constraint, leaving only minor gaps around failure behavior and sibling selection.

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 single 'query' parameter is already fully documented including the length bounds and the PII restriction. The description repeats the same PII guidance and adds no new syntax, format, or phrasing examples beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb ('Find') and resource ('residential appraisal services') plus the matching mechanism ('matching a short, general question to published service names and descriptions'). This is enough to distinguish it from a plain enumeration tool like list_appraisal_services, though that sibling is never named as the alternative.

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?

Gives implicit usage guidance by specifying the input should be a 'short, general question' and by warning against including a property address, phone number, or email address. It never says when to choose this over list_appraisal_services or what to do if the query is too narrow, so selection between siblings is left to inference.

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