Skip to main content
Glama

LocalSpot Trip

request_city

Ask LocalSpot Trip to add a city it does not plan yet (when list_destinations does not have it). Counts the request; the most requested cities are built first. Tell the traveller it is not covered yet and that the request was passed on. No personal data.

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>"
    },
    "name": "request_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. Krakow
countryNoCountry, e.g. Poland (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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, and it does disclose non-obvious behaviour: the call is a side-effecting vote, requests are aggregated and ranked to prioritise builds, and no personal data is retained. It stops short of saying whether the call is idempotent (does re-requesting the same city count twice) or what the response contains.

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?

Four short sentences, front-loaded with the action and its condition, then the side effect, then the user-facing obligation. No filler and nothing repeated from the schema.

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

Completeness5/5

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

For a two-parameter, non-annotated tool with a fully documented schema and no output schema, this covers everything an agent needs: when to call it, what it does downstream, and what to tell the user.

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%, with city and country both documented with examples, so the baseline is a 3. The description adds only a marginal constraint ('No personal data') rather than any extra meaning about format or expected values.

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

Purpose5/5

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

States a specific verb and resource ('add a city it does not plan yet') and scopes it to requests, which is distinct from list_destinations/list_cities. The agent can distinguish it from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger and negative condition: call this when list_destinations does not have the city, which simultaneously tells the agent to use list_destinations first. It also prescribes the follow-up behaviour toward the traveller, so the whole interaction path is specified.

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