Skip to main content
Glama

List Places

list_places
Read-onlyIdempotent

List countries, regions and cities that have marine contractors.

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

A4.2/5.0
Behavior3/5

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

The annotations already establish a safe, idempotent, closed-world read, and the description adds the useful constraint that results are limited to places with marine contractors. It does not explain result organization across the three geographic levels, ordering, or behavior when no places qualify.

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 front-loaded sentence communicates the operation, resource levels, and limiting condition without filler. Its brevity is appropriate for a zero-argument tool.

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 simple zero-parameter read, the description provides enough scope to select and invoke the tool correctly. Because there is no output schema, the lack of detail about whether places are returned separately or hierarchically, and how they are represented, remains a modest completeness 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?

There are no parameters, so the empty schema fully defines invocation and warrants the baseline score of 4. The description also confirms that contractor availability is a built-in scope constraint rather than a caller-supplied filter.

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?

The description combines a specific verb and resource—listing countries, regions, and cities—with the distinguishing constraint that each place has marine contractors. This clearly defines both the result set and its geographic scope.

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?

The marine-contractor qualifier establishes a clear use case: discovering supported geographic locations rather than retrieving an unrestricted place directory. It provides no explicit alternative, exclusion, or guidance for choosing among sibling 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