Skip to main content
Glama

guides

Today in ABQ's niche guides (green chile stew, posole, hot chocolate, late-night bars, just opened...). With a slug or words, returns that guide's picks and why.

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

Input Schema

NameRequiredDescriptionDefault
guideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at the return content ('picks and why') but does not disclose whether it is read-only, error behavior for unknown slugs, whether results are limited by date, or how the optional parameter changes the response.

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?

Two compact sentences with no filler; the parenthetical examples are helpful and brief. The structure could be improved by leading with the tool's action rather than the topical examples, but it is efficiently sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema and no annotations, the description covers the basic purpose and return content, but leaves meaningful gaps: what happens without a guide, what a slug looks like, and whether the response is a list or a single guide.

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 0% and the sole parameter is merely typed as string. The description compensates somewhat by explaining that the guide parameter accepts a slug or free-text words, which adds useful meaning beyond the schema, though it does not clarify slug format or how free-text matching works.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description indicates it returns a guide's picks and the reasoning behind them, and gives topical examples (green chile stew, late-night bars). But the opening phrase 'Today in ABQ's niche guides' is ambiguous about whether the tool lists available guides or fetches one specific guide, leaving the core operation somewhat vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It mentions passing 'a slug or words' but gives no explicit when-to-use guidance, no conditions for selecting this over siblings like search_places or events, and no explanation of what happens when the optional guide parameter is omitted.

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