Skip to main content
Glama

List Places

list_places
Read-onlyIdempotent

List countries, regions and cities that have opioid treatment providers.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and a closed-world scope, so the description need only add context beyond safety. It does so with a non-obvious selection rule: only places that actually have opioid treatment providers are returned, which changes how the agent should interpret an empty or short result. Return format is not described, but with zero parameters pagination concerns are minimal.

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 key scoping condition (places with providers) is placed where it is read first. Nothing could be removed without losing meaning.

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-parameter read-only list with full annotation coverage, the description covers the essentials: what is enumerated and what qualifies for inclusion. It leaves open whether results are names, identifiers, or nested hierarchy, which matters for chaining into a provider lookup, but that is a minor gap with no output schema to compare against.

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 no parameters, so the baseline is 4. The description correctly implies the call is unfiltered by saying it lists all eligible places, and nothing in the schema needs further explanation.

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 pairs the verb "List" with a precise resource: countries, regions and cities that have opioid treatment providers. It clarifies that "places" means a geographic hierarchy rather than arbitrary locations. It doesn't explicitly differentiate from siblings, but the siblings cover unrelated domains (products, courses, categories), so confusion risk is low.

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 implied: this is a discovery/lookup tool for the geography dimension of the dataset. The description does not state when to prefer it over a search tool or that the returned places can be used to filter providers, so the agent must infer the follow-up flow.

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