Skip to main content
Glama

Miami44 public directory

Get a Miami business site

get_business_site
Read-onlyIdempotent

Read one Miami business's site as plain text: what it is, where it is, what visitors can do with its official links, whether a verified owner runs it, and its sources. Details are public information and may be out of date.

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": {
      "slug": "<slug>"
    },
    "name": "get_business_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe business's link name from list_miami_businesses or find_miami_business

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 the safety profile is covered. The description goes beyond them by specifying the output is plain text, enumerating what is included, and adding a real behavioral caveat that the data is public and may be stale. It stops short of covering not-found behavior or output size limits.

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, no filler, and the primary purpose is front-loaded before the list of returned content and the staleness caveat. Every clause carries information an agent can use.

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?

This is a simple single-parameter read with full annotation coverage, and the description adequately conveys the return shape in prose as well as a data-freshness caveat. Only minor gaps remain, such as what happens when the slug does not resolve or how large the text response may be.

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 single required parameter is fully documented in the schema, including where its value comes from. The description adds no further meaning about slug format, case sensitivity, or validation, so the baseline of 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?

The description uses a specific verb ('Read one') and resource ('Miami business's site') and enumerates the content returned: identity, location, visitor actions via official links, verified-owner status, and sources. It implicitly contrasts with the list/find siblings by emphasizing a single site in plain text, but never names those siblings or states the contrast explicitly, keeping it short of the top mark.

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: an agent infers it should call this once it has a specific business in hand. There is no explicit when-to-use, when-not-to-use, or named alternative in the description itself; the routing hint ('from list_miami_businesses or find_miami_business') lives in the schema's slug description rather than the tool description.

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