Skip to main content
Glama

Foodeist

Find cities

find_cities
Read-onlyIdempotent

Look up cities Foodeist covers by name. Use it to disambiguate ("Portland" → Oregon or Maine) and get the slug for other tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results (default 5, max 10).
queryYesCity name or its beginning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that results are limited to the coverage set and carry slugs, but it says nothing about match behavior (prefix vs exact), ordering, or empty results beyond what the schema implies.

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?

Two short sentences, purpose first then the motivating use cases, with zero filler. Nothing could be cut without losing information.

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 two-parameter read-only lookup with rich annotations, this is close to complete: it says what is searched, why, and that a slug comes back. The only gap is the shape of returned city records, but no output schema exists to defer to, so a minor deduction.

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%, so both parameters (query, limit) are already documented, and the description adds only the disambiguation rationale for the query. It never mentions the limit parameter or ranking of results, so baseline 3 applies.

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?

"Look up cities Foodeist covers by name" gives a specific verb (look up) and resource (cities) plus the scope constraint that only covered cities exist. The city resource is clearly distinct from its restaurant/menu siblings, so an agent can route without opening another schema.

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

Usage Guidelines4/5

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

It states two concrete use cases: disambiguating same-named cities ("Portland" → Oregon or Maine) and obtaining the slug other tools need. It gives no explicit when-not guidance or named alternative, which keeps it short of a 5.

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