Skip to main content
Glama

LocalSpot Trip

open_nearby

Closed or a long line? Places open at a given time within a short walk (about 900 m) of a place or a point.

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": {
      "city": "<city>",
      "day": "<day>",
      "time": "<time>"
    },
    "name": "open_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
latNo
lonNo
cityYes
nearNoPlace name or sight name to search around
timeYesHH:MM
typeNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two real behavioral facts beyond the schema: the search radius (~900 m) and that results are filtered by open-at-time status. It omits what the response contains (name, distance, hours), how 'near' is resolved against lat/lon, and what happens when no places qualify, which matters for a tool with no output schema.

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 short sentences that are front-loaded with the motivating scenario and then state the core behavior. The opening question is slightly gimmicky but does earn its place by signaling intent; nothing else is wasted.

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

Completeness2/5

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

With 8 parameters, 25% schema coverage, no annotations, and no output schema, the description is too thin. It leaves the agent guessing about location precedence, result contents, and empty-result behavior for a moderately complex discovery tool.

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 only 25%, so the description needs to compensate and does not. It never explains the day/time pair beyond 'given time', the choice between 'near' and lat/lon, the meal/cafe/bar/any type filter, or the limit cap of 6; the only added semantics is the fixed radius, which is not even a parameter.

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 a specific resource and behavior: places that are open at a given time within roughly 900 m of a place or point. That is more than a restatement of the name. It does not explicitly differentiate itself from the sibling find_places, so it falls short of a 5.

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 framing question 'Closed or a long line?' implies the use case (checking what is currently available nearby), but there is no explicit when-to-use or when-not-to-use guidance and no reference to alternatives such as find_places or place_info. An agent must infer that this tool is preferred when opening hours and proximity matter.

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