Skip to main content
Glama

HumanFn

by com.humanfn
OverviewDiscussionsAdmin

Request an on-site task at an address (execution request)

request_execution
Idempotent

Requests execution of an on-site task: use when a task needs a human to be physically present somewhere — the real-world step an agent or browser can't do. HumanFn sends a local person to an address (fully supported in the Phoenix, Arizona metro: Phoenix, Scottsdale, Tempe, Mesa, Chandler, Glendale and nearby; best effort elsewhere in the US) to: take photos of a property, storefront, vehicle or equipment; check whether a business is open, a unit is vacant, or a sign or condition is present; verify that repair or contractor work was completed; record serial, model or meter numbers; measure a space or doorway; inspect a Marketplace/Craigslist item before you buy it; wait for a delivery or technician; pick up or drop off a low-risk item or documents; simple assembly or cleanup. Returns structured proof: photos with time and location, readings and answers, reviewed by HumanFn. Creates a request for a QUOTE. Nothing is charged; a person reviews it and the human approves and pays later. The Phoenix, Arizona metro area is fully supported. Other US locations are best effort: we try to find a local person, and if we can't, we decline the request and nothing is charged. Requests outside the US are declined. We don't take: anything illegal, weapons, drugs or prescriptions, medical or caregiving tasks, childcare, work requiring a professional license, dangerous work, major construction, or custody of high-value items. Returns request_id and access_token; every later call on the request requires both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesFull street address. The Phoenix, AZ metro is fully supported; other US locations are best effort; locations outside the US are declined.
objectiveYesWhat must be true or be captured when the job is done. Be specific: what to photograph, measure, check, deliver.
complete_byNoDeadline for the outcome. ISO 8601 with offset (Phoenix is UTC-07:00).
access_notesNoGate codes, who to ask for, where to park, hours.
contact_nameNoThe customer's name, for the quote.
contact_emailYesThe human customer's email. Quotes and status links are sent here.
contact_phoneNoThe customer's phone number, for urgent questions about the task.
max_budget_usdNoThe most the customer is willing to pay, in US dollars. Quotes above it are flagged.
client_request_idNoYour idempotency key. Retrying with the same key returns the same request instead of creating a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / contact_name / description
      Added value: +"The customer's name, for the quote."
    • addedInput schema / properties / contact_phone / description
      Added value: +"The customer's phone number, for urgent questions about the task."
    • addedInput schema / properties / max_budget_usd / description
      Added value: +"The most the customer is willing to pay, in US dollars. Quotes above it are flagged."
  2. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"Full street address in the Phoenix, AZ metro area."New value: +"Full street address. The Phoenix, AZ metro is fully supported; other US locations are best effort; locations outside the US are declined."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true) by disclosing the quote-only/no-charge model, human review and later approval/payment, regional coverage and decline behavior, prohibited categories, and the returned request_id + access_token required for later calls. This is exactly the behavioral context an agent needs before invoking.

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?

Purpose is front-loaded and the sentence earns its detail, but the long single-sentence job-type enumeration and the duplicated Phoenix-metro statement (also in the address field) add bulk. Efficient overall, slightly over-packed.

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?

With no output schema, the description fills the gap by explaining what is returned (request_id and access_token) and how later calls must use it. Combined with coverage of pricing model, geography, and exclusions, an agent has everything needed to call this correctly.

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 all nine parameters are already documented in the schema; the description mainly restates geography already present in the address field and adds the access-token follow-up requirement. Baseline 3 is appropriate when the schema carries parameter semantics.

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 and resource ('requests execution of an on-site task') and immediately scopes it as the physical real-world step an agent or browser cannot perform. The rich enumeration of jobs makes the tool's remit unmistakable and distinguishes it from pure digital siblings like find_human_function or get_request.

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 strong when-to-use context ('use when a task needs a human to be physically present') plus explicit when-not exclusions (illegal, weapons, drugs, medical, childcare, licensed/dangerous work) and geographic limits (Phoenix fully supported, US best effort, non-US declined). It does not name a sibling alternative to use instead, which is the only gap.

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

All HumanFn toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources