Skip to main content
Glama

Find a suburb

find_suburb
Read-onlyIdempotent

Finds Sydney suburbs by name, spelled as find_homes takes them in profile.about.suburbs.

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": {
      "text": "<text>"
    },
    "name": "find_suburb"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat the buyer called it: at least a couple of letters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real value by naming the dataset scope (Sydney suburbs), which the annotations do not specify. It omits whether partial input yields multiple matches, whether matching is fuzzy or prefix, and what the result contains — gaps the annotations do not fill.

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?

One sentence, front-loaded with the verb and resource, with no filler. The trailing clause about find_homes' profile path is dense and slightly cryptic for an agent unfamiliar with that output shape, which keeps it short of a 5.

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 one-parameter read lookup with full schema coverage and a complete annotation set, the definition supplies the essentials: dataset scope, match basis, and expected spelling. The main remaining gap is the return shape (single match vs. list, behavior on no match), which is not covered by an output schema.

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% and the schema already defines 'text' as what the buyer called the suburb with a minimum of a couple of letters, so the baseline would be 3. The description goes beyond that by prescribing the target spelling convention — the same form find_homes expects in profile.about.suburbs — which is a genuine, non-redundant constraint on parameter values.

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?

Specific verb (Finds) and resource (Sydney suburbs by name), with an added scope fact — Sydney only — that separates it from find_place and find_school. It does not explicitly contrast itself with those siblings, but the resource is distinct enough that an agent can route correctly.

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?

Usage is only implied: the reference to how find_homes reads profile.about.suburbs suggests this is a preparatory lookup for filtering homes, but there is no explicit 'use when' or 'use instead of find_place' statement. An agent must infer the call context.

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