Skip to main content
Glama

List areas

list_areas
Read-onlyIdempotent

List the areas Ippuku knows (neighborhoods of big cities such as Shinjuku, Namba or Gion, and smaller towns such as Kamakura), with their slug, center, radius and the number of places per category. Use it to find the slug to pass as area to find_nearby_places, or to see where Ippuku has data.

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_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes
attributionYesData attribution. Show it with the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read. The description adds useful context about what 'areas' means and what metadata is returned, though it does not discuss pagination or limits, and the output schema already covers return shape.

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 well-structured sentences: the first defines the resource and returned data, and the second states the practical use. The examples are compact and directly support the definition.

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

Completeness5/5

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

With zero parameters, a full output schema, and clear annotations, the description provides everything needed to select and call the tool correctly. It also routes the agent toward the relevant sibling, find_nearby_places.

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 has no parameters, so there is no parameter semantics to explain. The baseline for zero parameters 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?

The description uses a specific verb and resource ('List the areas Ippuku knows') and clarifies the granularity with concrete examples such as Shinjuku and Kamakura. It also lists the returned fields and thus makes clear how this differs from the place-lookup siblings.

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 gives a clear primary use case: obtaining an area slug to pass to find_nearby_places, and a secondary use case for exploring data coverage. There is no explicit 'when not to use' guidance, but for a zero-parameter listing tool the intended role is unambiguous.

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