Skip to main content
Glama
Sign In

GISDB

by io.gisdb
OverviewDiscussionsAdmin

suggest_addresses

Read-onlyIdempotent

Search retained county-roll address candidates for partial queries and typos. A suggestion is a candidate identity, not verified owner authority or financial eligibility.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of candidate suggestions to return (default: 5)
queryYesAddress query or partial street name (e.g. '3731 Andrson Ave', 'Anderson Ave', '810 Lindsay')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds a meaningful trust caveat that a suggestion is only a candidate identity, not verified owner authority or financial eligibility; it does not cover pagination or return format, but that is less critical here.

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 action and scope, and the caveat is compact. No redundant wording.

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-parameter read-only suggestion tool with full schema coverage and annotations, the description covers purpose, query tolerance, and the key limitation. It could be slightly more complete by naming when to prefer a different address or eligibility tool, but nothing essential is missing.

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 schema documents query and limit. The description still adds useful query semantics by saying it handles partial queries and typos, which goes beyond the schema's examples.

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, "Search," and resource, "retained county-roll address candidates," and scopes it to partial queries and typos. It also distinguishes the result from verified owner authority or financial eligibility, though it does not name a specific sibling 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 a clear use context for partial queries and typos, but does not state when not to use it or name alternatives such as check_eligibility or check_portfolio_address_status. Guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GISDB toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources