Skip to main content
Glama

List Places

list_places
Read-onlyIdempotent

List countries, regions and cities that have pest control companies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_places"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety envelope is fully covered without the description's help. The description's one added behavioral fact is the scoping filter — only places that actually have pest control companies are returned — which is genuinely useful and prevents an agent from assuming a full global gazetteer. It says nothing about ordering, result shape, or pagination.

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?

A single sentence with no filler, and the qualifying constraint is packed into the same clause rather than buried. Nothing could be removed without losing information.

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

Completeness3/5

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

For a trivially simple, zero-parameter, read-only tool the description is close to sufficient, but there is no output schema, so the description carries the burden of describing return values — it does not say whether the three geographic levels are returned flat, nested, or as separate fields, nor how large the list is. A short note on the result structure would close the remaining gap.

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?

The tool takes zero parameters, so per the baseline this lands at 4 — there is no parameter semantics to explain and the description doesn't misleadingly imply any inputs. An agent reading it will correctly call it with no arguments.

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 gives a specific verb ('List') and enumerates the concrete resource set — countries, regions, and cities — plus a qualifying condition (places that have pest control companies). That is enough for an agent to distinguish it from siblings like list_products or search_listings. It stops short of 5 only because it doesn't acknowledge any sibling or the relationship between the three geographic levels.

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?

There is no when-to-use guidance: nothing says this is the entry point for discovering valid geography values, and nothing excludes it from use as a general search. The zero-parameter shape makes the invocation fairly obvious, but the description itself offers no routing context relative to search_listings or the other list_* tools.

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