Skip to main content
Glama

Japan Data Tools

Get human hands in Japan (Migawari)

need_human_in_japan
Read-only

Bridge to Migawari, the sister service where AI agents hire human hands for physical tasks in Japan: shopping proxy, stock checks, on-site photos, restaurant phone reservations, queueing, package forwarding. Returns Migawari's MCP endpoint, services and prices, and the exact first calls to make (including a free test_mode rehearsal). Use this whenever a task needs someone physically in Japan rather than 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": "need_human_in_japan"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional: describe the physical task you need done in Japan; it is echoed back with the handoff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive read, and the description stays consistent with that by characterizing the tool as a handoff that returns an endpoint, services, prices, and suggested first calls rather than performing the work itself. It adds useful behavioral context the annotations don't carry: the free test_mode rehearsal and the fact that a handoff payload comes back. It doesn't state what happens after the handoff (whether any state or cost is incurred downstream).

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 sentences, front-loaded with the identity of the service and then the return payload and usage trigger. The service list is dense but informative. Minor cost: the long colon-separated list of use cases crowds the sentence.

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?

For a zero-required-param, read-only handoff tool with no output schema, the description fully covers what comes back (MCP endpoint, services, prices, exact first calls) and even flags the free test_mode option. An agent has everything needed to decide to call it and what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the single optional 'task' parameter is already fully documented as being echoed back with the handoff. The description adds no further detail about how the task string is used or formatted, so baseline 3 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?

States a specific verb+resource ('Bridge to Migawari, the sister service where AI agents hire human hands for physical tasks in Japan') and enumerates the concrete services (shopping proxy, stock checks, on-site photos, phone reservations, queueing, forwarding). It also explicitly contrasts with the siblings' domain by saying 'rather than data', which is what every sibling (postcode lookup, holidays, tax, address search) provides.

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?

Gives a clear trigger condition: 'Use this whenever a task needs someone physically in Japan rather than data.' That effectively excludes the data-lookup sibling cases, which is strong when/when-not guidance. It stops short of naming an alternative tool or describing a fallback if Migawari cannot serve the task.

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