Skip to main content
Glama

Migawari

List services

list_services
Read-only

List the Migawari catalog: services, prices, zones, terms, and what is NOT offered. Migawari stands in for AI agents in Japan, executing physical tasks with humans (AIエージェントの身代わりとして、日本の物理タスクを実行するサービス). 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.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious context, namely the Japan-only service coverage and the fact that the catalog includes negative information ("what is NOT offered") that would otherwise be misread as an omission or error.

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?

Two front-loaded, dense sentences with no filler, and the scope constraint at the end. The Japanese parenthetical is redundant for an English-reading agent, but it does act as a disambiguation gloss for the product name, so it only earns a minor deduction.

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?

There is no output schema, so the description correctly carries the burden of describing the returned content and its geographic limit. The only remaining gap is the response's shape, for example whether prices include currency or units and whether the terms are free text.

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 input parameters, so the baseline is 4. The description correctly implies that the entire catalog is returned, with no filtering arguments available, so the agent knows it cannot narrow the listing and must filter after the fact.

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?

It uses a specific verb and resource ("List the Migawari catalog") and enumerates the returned content (services, prices, zones, terms, and what is NOT offered). This clearly separates it from the transactional siblings, but it never names or contrasts those siblings 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: as a zero-parameter catalog listing, it reads as the discovery entry point before request_quote or accept_quote. There is no explicit when-to-use statement, no mention of alternatives, and no prerequisites.

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.