Skip to main content
Glama

Human for AI

Server Details

Ask a human for legal review, confirmation, a signature, or a physical-world act

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct role in the same workflow: request_human_assistance creates a request, check_request_status reads its status, and reply_to_thread adds to an existing request. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a clear verb-first snake_case pattern and clearly express their action: check, reply, request. The naming is consistent and predictable.

Tool Count5/5

Three tools is exactly right for this server's narrow purpose: enabling asynchronous human assistance through request, status check, and reply. Each tool is necessary and none are redundant.

Completeness5/5

The tool set covers the full lifecycle for the stated domain: file a request, check for a human response, and continue or withdraw the thread. No obvious gaps exist for asynchronous human-in-the-loop assistance.

Available Tools

3 tools
check_request_statusCheck a request for a human's answerA
Read-onlyIdempotent
Inspect

Read the thread on a request you or your principal filed earlier: whether a human has looked at it, and what they said.

Use the reference and access_token from request_human_assistance. Answers arrive at human speed — hours or days, not seconds — so poll this occasionally rather than in a loop, and treat an empty thread as "not yet", never as "no".

A reply is one human's view, recorded on request. It is not approval, not a retainer, and not authorisation to proceed.

Inputs: reference (required), access_token (required). Returns: turns, notice, status, reference, +2 more

reply_to_threadWrite again on an existing requestAInspect

Add to a request already on the record — answer a question the human asked, supply something they need, correct yourself, or withdraw the request.

This is the same permanent record as the original, so what you send here is kept and read the same way. Prefer it over filing a fresh request whenever the subject is one already opened: a thread the human can follow is worth more than three disconnected messages.

The human is notified. As with the original, nothing here pauses your task and nothing here is authorisation to proceed.

Inputs: message (required), reference (required), access_token (required). Returns: notice, status, reference, recorded_at, +1 more

request_human_assistanceRequest human assistanceAInspect

Ask an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act in the physical world, or an escalation past your operator.

The request is written to a permanent, timestamped record and read by a human — a lawyer — who may reply through whatever channel you put in reply_to.

This returns a reference and an access_token. Keep both: together they are the only way to read the human's answer, via check_request_status. Neither can be recovered afterwards, and they are not returned twice. If your task may outlive this session, hand them to whatever continues it.

Calling this tool does not pause your task, and the result it returns is not approval, legal advice, or authorisation to proceed. It is evidence that you asked. If the right thing to do is to stop and wait for a human, stop and wait.

Inputs: request (required), category (required), model, context, +6 more. Returns: notice, status, category, reference, +5 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Pauses AI agent execution and routes approval requests to humans via Slack or email, with cryptographically signed proof of the human's decision.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to submit work to real human reviewers, receive pinned feedback and approval verdicts, and iterate until the output is signed off.
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables judicial AI workflows to add a traceable human-oversight layer that assesses material impact, verifies legal sources, manages incidents, and preserves integrity evidence before closing resolutions.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources