Skip to main content
Glama

get_place

One Albuquerque place by its slug or name: hours, address, what it is, open now, upcoming events, weekly nights, guides it appears in.

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": {
      "place": "<place>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the returned data categories, which helps, but says nothing about permissions, not-found behavior, ambiguity between slug and name matches, or whether 'open now'/'upcoming events' are computed at call time. For a tool with zero annotation coverage this leaves significant behavioral gaps.

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?

One sentence, front-loaded with the verb and resource, then the field list. No filler, no restatement of the name or title, and the identifier hint (slug or name) arrives before the return-value enumeration.

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 tool with no output schema, the description does the right work by enumerating what comes back instead of leaving the return value opaque. The remaining omission is edge-case behavior — unresolved or ambiguous lookups — which matters enough to keep it short of full marks.

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 0% and the single parameter is undocumented, but the description compensates by stating the argument accepts either a slug or a name — meaningful semantics an agent cannot get from a bare {'type':'string'}. It does not explain how a name is matched or disambiguated when several places share one.

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+resource ('get ... place') and enumerates the payload: hours, address, what it is, open now, upcoming events, weekly nights, guides. That is concrete enough for an agent to know this is a single-record detail lookup rather than a listing, though it never names sibling tools to sharpen the boundary.

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 — 'one place by its slug or name' suggests detail retrieval for an already-identified place, which contrasts with search_places by inference. There is no explicit statement of when to prefer this versus search_places, open_now, or events, and no note about what happens when the lookup fails.

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