Skip to main content
Glama

search_places

Search Albuquerque places (restaurants, bars, breweries, coffee, venues, shops) by words, kind or neighborhood.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
neighborhoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read operation but does not state read-only semantics, does not describe the result shape (names, ratings, addresses?), does not disclose that results appear to be capped by a default limit of 15, and does not say what happens when no matches exist.

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?

A single front-loaded sentence with no filler; the covered categories and search axes are packed efficiently. Slightly more room could have been spent on the alternative-tool routing rather than the long parenthetical category list.

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

Completeness1/5

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

For a 3-parameter tool with zero schema coverage, no annotations, and no output schema, the definition is far too thin: no limit/pagination behavior, no result format, no guidance relative to get_place or open_now. An agent cannot confidently predict what it will get back or how many.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate. It maps roughly to query ("words"), neighborhood, and "kind", but leaves the relationship between "words" and "kind" ambiguous and never mentions the limit parameter or its default of 15. The most important behavioral parameter is undocumented in both places.

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?

A specific verb+resource ("Search Albuquerque places") with an enumerated set of covered categories (restaurants, bars, breweries, coffee, venues, shops) and the search axes (words, kind, neighborhood). It does not differentiate from the sibling get_place, which reads as a separate detail-fetch tool.

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?

The description implies usage (search by words/kind/neighborhood) but offers no explicit when-to-use guidance, no exclusions, and no mention of when to switch to get_place for a specific place or to open_now for availability. Nothing tells the agent under what conditions this tool is the right 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