Skip to main content
Glama

HumanEndpoint

Request human task quote

human_request_quote
Destructive

Submit a request for human-reviewed terms for a real-world task whose cost depends on scope, feasibility, urgency or conditions. This sends the request into a HumanEndpoint workflow for review by a human operator, but does not commit funds or start execution. HumanEndpoint returns commercial terms that can be accepted or declined before payment. Provide callback_url to receive signed quote.offered or quote.declined webhooks instead of relying only on polling. Suitable tasks include calling a business for current price, stock, lead time or availability; retrieving information only available by phone; verifying a real-world fact; checking AI output; applying human judgement; doing bounded research; or carrying out a physical-world task. If no named service matches, set service_slug to custom-human-task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service_slug": "<service_slug>",
      "objective": "<objective>",
      "deliverables": "<deliverables>"
    },
    "name": "human_request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectiveYes
requesterNo
constraintsNo
deadline_atNo
callback_urlNo
deliverablesYes
service_slugYes
max_budget_usdcNo
max_expenses_usdcNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / callback_url
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses the async workflow (HumanEndpoint review), that no funds are committed and no execution begins, that the response is commercial terms which can be accepted or declined, and that webhooks quote.offered/quote.declined can replace polling. Gaps remain: no mention of whether submission itself costs anything, idempotency or duplicate submissions, or turnaround expectations. There is also mild tension with openWorldHint=false given the stated phone/real-world task scope, though the tool itself only brokers to a human endpoint, so it is not a direct contradiction.

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?

Front-loaded with the core action and the no-commitment guarantee, then workflow, then usage examples, then the fallback rule. The suitable-task list is long but earns its place by disambiguating scope. Minor trimming is possible but nothing is padded or repetitive.

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

Completeness3/5

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

For a 9-parameter, nested-object mutation with no output schema, the description covers the workflow and side-effect profile well. It does not cover the quote object the agent receives (fields, validity window, pricing shape, why a quote may be declined) nor the budget/expense/deadline semantics, which an agent needs to fill the request correctly.

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?

Schema description coverage is 0% across nine parameters, so the description must carry the load. It only explains callback_url (signed quote.offered/quote.declined webhooks) and service_slug (custom-human-task fallback). max_budget_usdc, max_expenses_usdc, deadline_at, requester, constraints, objective and deliverables all remain undefined in both places, including whether budgets are caps that trigger decline.

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 verb and resource are explicit ('Submit a request for human-reviewed terms') and the description immediately pins the lifecycle stage: it obtains a quote, does not commit funds, and does not start execution. That cleanly separates it from human_create_job (execution) and human_get_quote (retrieval) without the agent needing to open either schema.

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?

It enumerates concrete suitable cases (price/stock/lead-time calls, phone-only information, fact verification, AI output checking, bounded research, physical-world tasks) and gives a routing rule for unmatched services via service_slug=custom-human-task. It also steers toward callback_url over polling. What is missing is an explicit when-not: nothing says what to do after acceptance (presumably human_create_job) or which tasks should skip quoting entirely.

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