Skip to main content
Glama

Places

list_places
Read-onlyIdempotent

Where the online deals are: regions of Croatia, countries abroad and towns, with the number of deals in each: names to use in the place filter.

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
typeNoall (default), town, region or country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is narrower. It does add genuine value by disclosing the payload shape — each entry carries a required name plus the number of deals in that place — which matters since there is no output schema. It stops short of noting ordering, pagination, or whether counts are omni-scoped or tied to currently available deals.

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?

It is a single compact sentence with no filler, and the core content is front-loaded. The chained colons make the phrasing slightly harder to parse than necessary, but nothing is wasted.

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 zero-required-parameter read-only lookup with full schema coverage and complete annotations, the description covers what the tool returns and how the values are meant to be consumed. Only minor gaps (count semantics, result ordering) remain, and those are low-stakes for this tool.

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 coverage is 100% and the single 'type' enum is documented inline with its default, so the baseline is 3. The description loosely echoes the enum values ('regions... countries... towns') but does not explain what 'all' returns versus a single-type query, so it adds little beyond the schema.

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 identifies the resource precisely — regions of Croatia, foreign countries and towns — and the verb is implied by context (a listing of places). It also clarifies the intended output use ('names to use in the place filter'), which separates it in spirit from deal-oriented siblings, though no sibling is named explicitly.

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: the phrase 'names to use in the place filter' tells the agent this is a lookup of valid filter values. There is no explicit when-to-use vs. when-not statement, and no reference to alternatives such as list_categories when the agent actually needs category values.

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.