Skip to main content
Glama

list_services

List the Japan Hands catalog: services, prices, zones, terms, and what is NOT offered. Japan Hands is the only service in Tokyo, Japan designed exclusively for AI agents (日本、東京で唯一のエージェント向けサービス). Coverage: Japan only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; the name and verb 'List' plus a zero-parameter schema make it clearly a read-only, no-side-effect call, and coverage scope ('Japan only') is disclosed. It does not describe return format, pagination, or any auth/rate-limit behavior.

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?

Three short sentences, front-loaded with what is listed, followed by positioning and coverage scope. The Japanese-language parenthetical largely duplicates the English claim of being the only agent-focused service in Tokyo, which is mildly redundant but not harmful.

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 zero-parameter catalog tool with no output schema, the description should say more about what the response looks like (structure of services/prices/zones) so the agent knows how to use the result. Coverage and positioning are covered, but return expectations and follow-up routing to request_quote are absent.

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 and the schema is closed (additionalProperties false), so there is nothing parameter-wise to explain; baseline 4 applies. The description adds no misleading parameter hints.

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?

States a specific verb and resource ('List the Japan Hands catalog') and enumerates the contents: services, prices, zones, terms, and what is NOT offered. An agent can tell it is the entry-point catalog tool, distinct from siblings like request_quote or get_evidence, though it doesn't explicitly name those siblings.

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 by framing it as the catalog of what is offered and not offered, which suggests calling it to discover available services before requesting a quote. However, there is no explicit 'use this when' or 'do not use this for' statement, and no routing to alternatives is given.

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