Skip to main content
Glama

Miami44 public directory

Find a Miami business

find_miami_business
Read-onlyIdempotent

Search Miami44's business sites by name. Returns each match's name, link name (slug) and site URL.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPart of the business name, for example 'casaplanta'

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 readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered elsewhere. The description adds the returned fields (name, slug, URL), which is helpful context, but says nothing about result-count limits, matching semantics (prefix vs substring) or ordering.

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 tightly written sentences: the first states the action and scope, the second states what comes back. No padding or redundant restatement of the title.

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 single-parameter read-only lookup with full annotation coverage, the description covers purpose, input meaning and return shape, so an agent can call it confidently. The only gap is behavioral detail about match breadth, limits and ordering, which is minor at this complexity.

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 coverage is 100% and the schema already explains the query is a partial business name with an example. The description's "by name" only loosely reinforces that the term is a name fragment, adding little beyond the schema, so the baseline 3 applies.

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 and resource ("Search Miami44's business sites by name") and distinguishes itself from the sibling list_miami_businesses by framing the operation as a name lookup rather than a listing. It does not explicitly name the siblings, so it stops short of a 5.

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?

The "by name" phrasing and the schema's "part of the business name" imply this is the tool for partial-name lookups, and the contrast with a list tool is implicit. However, there is no explicit when-to-use/when-not guidance or named alternative such as listing all businesses or fetching a site by slug.

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