Skip to main content
Glama

City guide

get_city_guide
Read-onlyIdempotent

Practical guidance for a Florida city Quo serves: getting around, the airport transfer, neighborhoods, and dining/nightlife/culture picks. Same content as the site's public guide pages.

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": {
      "citySlug": "<citySlug>"
    },
    "name": "get_city_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
citySlugYesOne of: miami, miami-beach, fort-lauderdale, palm-beach, west-palm-beach, boca-raton, wellington, naples, key-west, orlando, tampa

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 adds genuinely useful context beyond them: the content mirrors the site's public guide pages, telling the agent the material is static and generic rather than personalized or live. It does not discuss freshness, pagination, or response shape, but with full annotation coverage that is a minor gap.

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, both earning their place: the first front-loads the resource and its content categories, the second immediately qualifies the nature of the content. No filler, no repetition of the title or schema.

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-only lookup with no output schema, the description does the important work of sketching what the guide contains, so an agent knows what a call will yield. The remaining unknown is structural detail of the response (format, length), which is acceptable given the simplicity and the closed enum of cities.

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 description coverage is 100% and the single citySlug parameter has a fully enumerated list of accepted values, so the schema carries all the meaning needed. The description adds nothing about the parameter beyond implying that only Florida cities Quo serves are valid, which the enum already establishes. 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?

The description names the resource (practical guidance for a Florida city Quo serves) and enumerates the content categories it covers: getting around, airport transfer, neighborhoods, dining/nightlife/culture. That is enough to distinguish it from the ride- and account-oriented siblings, though it never explicitly contrasts itself with any of them.

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 can infer this is the tool for destination questions about a served city. There is no explicit when-to-use statement, no exclusion such as 'not for ride booking or account questions, use reserve_ride/get_quote', and no mention of when ask_concierge would be the better choice.

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