Skip to main content
Glama
upamune
by upamune

human_hand_tool

Execute physical tasks by sending instructions to a human operator through a Streamlit interface. Use this tool to perform manual actions that require human dexterity.

Instructions

人間が手を使って簡単な物理的操作を実行します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instructionYes

Implementation Reference

  • The primary handler function for the 'human_hand_tool' tool. It is decorated with @mcp.tool() which registers it with the FastMCP server. The function generates a unique task ID, stores the instruction in the database via db_utils, polls for completion using wait_for_task_completion, and returns the result.
    @mcp.tool()
    async def human_hand_tool(instruction: str, ctx: Context) -> Dict[str, str]:
        """人間が手を使って簡単な物理的操作を実行します。"""
        task_id = str(uuid.uuid4())
        formatted_instruction = f"✋ 手を使って操作: {instruction}"
    
        # タスクをデータベースに追加
        db_utils.add_task(task_id, formatted_instruction)
    
        # ログ出力
        sys.stderr.write(f"Human task created: {task_id}. Waiting for completion...\n")
    
        # 結果を待機(非同期ポーリング)
        result = await wait_for_task_completion(task_id)
    
        # ログ出力
        sys.stderr.write(f"Human task {task_id} completed.\n")
    
        return {"result": result}
  • The input and output JSON schema definition for the 'human_hand_tool' in the HUMAN_TOOLS list, defining the expected parameters and return structure.
    {
        "name": "human_hand_tool",
        "description": "人間が手を使って簡単な物理的操作を実行します。",
        "input_schema": {
            "type": "object",
            "properties": {
                "instruction": {"type": "string", "description": "実行する物理的操作の指示"}
            },
            "required": ["instruction"]
        },
        "output_schema": {
            "type": "object",
            "properties": {
                "result": {"type": "string", "description": "操作の結果"}
            },
            "required": ["result"]
        }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions '簡単な物理的操作' (simple physical operations) but doesn't specify what types of operations are supported, any limitations (e.g., precision, strength), safety considerations, or expected outcomes. This leaves significant gaps in understanding how the tool behaves in practice.

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?

The description is a single, efficient sentence in Japanese that directly states the tool's purpose without unnecessary elaboration. It's appropriately front-loaded and wastes no words, though it could benefit from more detail given the lack of annotations and schema coverage.

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

Completeness2/5

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

Given the tool's complexity (a physical operation tool with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It doesn't explain what the tool returns, how errors are handled, or provide enough detail for an agent to use it effectively in context with sibling tools.

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

Parameters2/5

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

The schema has 1 parameter with 0% description coverage, so the description must compensate. It provides no information about the 'instruction' parameter—what format it should take, examples of valid instructions, or how it influences the tool's behavior. This fails to add meaningful semantics beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as '人間が手を使って簡単な物理的操作を実行します' (a human performs simple physical operations using hands), which provides a general verb+resource combination. However, it's vague about what specific operations are possible and doesn't distinguish this tool from sibling tools like human_ear_tool or human_eye_tool, which likely involve different sensory modalities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, constraints, or scenarios where this tool would be preferred over other human_* tools, leaving the agent with no usage context beyond the basic purpose statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/upamune/human-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server