Skip to main content
Glama

NeedHuman

by io.github.MariusAure

need_human

Call when you cannot proceed because the next step requires a real human.

USE WHEN you are blocked by:

  • Terms of Service or legal agreements requiring a natural person

  • Account creation that needs identity verification or CAPTCHA

  • Authentication requiring human identity (BankID, SMS 2FA, OAuth)

  • Forms requiring human verification or a physical-world action

  • Content behind a login wall you cannot access

  • Any step requiring legal personhood, physical presence, or human identity

DO NOT USE for: sending messages, making HTTP requests, writing code, or any task you can complete with your existing tools.

The human is a paid worker (billed per task), not your operator. Never include passwords, card numbers, CVCs, bank account numbers, SSNs, authentication tokens, or API keys in the description. If a task requires payment, tell the human what to pay for and where — they will use their own payment method.

Format your description as numbered steps, one instruction per line. Put each URL on its own line. End with "REPLY WITH:" listing expected deliverables.

Example: STEPS:

  1. Create account at https://example.com/signup

  2. Accept the terms of service. REPLY WITH: confirmation URL, account ID

Free tier included on registration. Each task costs 1 credit. Returns 402 when credits are exhausted. Fastest during European business hours (CET). Tasks submitted outside these hours may take longer. Typical completion: 2-30 minutes. Use check_task_status to poll.

Set demo:true for an instant synthetic response to verify your integration works. No credits consumed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
demoNoSet to true to get an instant synthetic response. No credits consumed, no real human involved. Use to verify integration works before submitting real tasks.
urgencyNoimmediate = target completion within 5 minutes. normal = within 60 minutes.
action_typeNoCategory: 'create_account', 'accept_terms', 'complete_web_action', 'bankid_auth', 'verify_identity', 'form_submission'
descriptionYesWhat you need the human to do. Include URLs, account details, and expected outcome.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels. It discloses billing ('paid worker (billed per task)'), security constraints ('Never include passwords...'), latency ('Typical completion: 2-30 minutes'), regional availability ('Fastest during European business hours'), credit exhaustion ('Returns 402 when credits are exhausted'), and demo behavior ('demo:true for an instant synthetic response'). This is exemplary transparency.

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 long, but every sentence serves a purpose, with clear headings and an example that clarifies expected formatting. It is well-structured and front-loaded with the core purpose. Slightly verbose in a few places (e.g., availability timing), but justified given the tool's complexity and number of constraints.

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?

Given the tool's complexity, absence of annotations, and lack of output schema, the description covers all necessary context: task formation, billing, timing, failure (402), demo mode, polling alternative, and security constraints. It explains expected deliverables via 'REPLY WITH' instructions, making it fully self-contained for an agent to invoke correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by detailing the format for the 'description' parameter ('numbered steps', 'Put each URL on its own line', 'End with REPLY WITH:') and explaining the demo parameter's purpose and cost implications. This enriches understanding beyond the schema's per-field descriptions.

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 clearly states the tool's purpose: 'Call when you cannot proceed because the next step requires a real human.' It specifies the resource (a human worker) and action (delegating a task), and distinguishes it from siblings like check_task_status by explicitly naming them: 'Use check_task_status to poll.'

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

Usage Guidelines5/5

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

The description provides explicit 'USE WHEN' and 'DO NOT USE FOR' conditions, listing specific scenarios like ToS agreements, identity verification, and login walls, and excluding tasks like sending messages or making HTTP requests. It also names an alternative tool, check_task_status, for polling, making usage guidance unambiguous.

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

All NeedHuman toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool serves a clearly distinct purpose: need_human submits a new human task, check_task_status polls a specific task's status and result, and list_tasks reviews all submitted tasks. There is no overlap or ambiguity between them.

Naming Consistency4/5

All tool names use lowercase snake_case and follow a verb_noun structure (need_human, check_task_status, list_tasks). However, 'need_human' is less action-oriented compared to the other two, which slightly breaks the predictable pattern of task-centric operations.

Tool Count5/5

With 3 tools, the server is well-scoped for a targeted service: submit a human task, check one task, and list all tasks. This is a minimal but complete set without unnecessary bloat.

Completeness5/5

The tool set covers the full lifecycle of a human-assisted task: creation (need_human), status/result retrieval (check_task_status), and history review (list_tasks). No essential operation is missing for the domain.

Resources