Skip to main content
Glama

Miami44 public directory

List Miami businesses

list_miami_businesses
Read-onlyIdempotent

List Miami44's business sites, optionally narrowed by words, neighborhood (for example 'Wynwood') or category (for example 'restaurant'). Returns each business's name, link name (slug), site URL, category, neighborhood and whether a verified owner runs it. The reply gives total, has_more and next_offset; pass offset to read the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_miami_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return in one page
queryNoWords to match in the name, category or neighborhood
offsetNoHow many results to skip; use next_offset from the previous reply
categoryNoExact category, for example restaurant, bar, gallery
neighborhoodNoExact neighborhood name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the exact fields returned per record (name, slug, site URL, category, neighborhood, verified owner) and the pagination contract (total, has_more, next_offset). That pagination detail is the kind of thing annotations cannot express.

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?

Three sentences, front-loaded with the resource and filters, then the return shape, then the pagination instruction. Every clause carries information an agent needs; nothing is repeated from the schema verbatim.

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?

With no output schema, the description carries the burden of describing returns and does so explicitly, and it covers pagination end-to-end. The only gap is comparative guidance against the two sibling lookup tools, which would fully close the loop for tool selection.

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 baseline would be 3, but the description goes further by naming concrete values ('Wynwood', 'restaurant') for neighborhood and category and by explaining that offset comes from the previous reply's next_offset. This meaningfully reinforces how to wire the pagination parameters together.

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 ('List Miami44's business sites') plus the axes it can be narrowed by, which is far more informative than the bare title. It does not, however, differentiate itself from the sibling find_miami_business, so an agent must infer that this is the enumerating variant.

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 implied: the optional narrowing filters and the 'pass offset to read the next page' instruction tell an agent how to page through results. There is no explicit guidance on when to choose this over find_miami_business or get_business_site, and no stated exclusions.

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