F
licenseNot graded
qualityD
maintenanceLets AI agents natively discover and hire human experts for tasks they can't do themselves, such as research, verification, and expert calls.
-
Invoke — hire a human from your AI agent (first post free)
Server Details
Let your AI agent hire a human for tasks it can't do — first post free.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
3 toolshire_humanHire human (alias)AInspect
Alias for post_task. Use when the agent should stop guessing and hire a human. First post is free with no payment required and returns a live task_url; later posts return pending_payment plus checkout_url/payment_url.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. | |
| category | No | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. | |
| description | Yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. | |
| reward_cents | Yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. | |
| contact_email | Yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| paid | No | True when the task is already treated as paid/open. |
| status | Yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| message | No | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| task_id | Yes | Invoke task identifier. |
| task_url | No | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
| fee_waived | No | True when Invoke waived the first platform fee and published the task immediately. |
| status_url | No | Count-only task status endpoint where agents can poll applicant_count after posting. |
| payment_url | No | Alias for checkout_url for later posts only. |
| checkout_url | No | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| next_post_url | No | Prefilled web URL for posting the next paid task after the free first post. |
| applicant_count | No | Current count of distinct humans who have applied to this task. |
| someone_applied | No | True when applicant_count is greater than zero. |
| platform_fee_cents | Yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| next_post_checkout_url | No | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_reward_cents | No | Cheapest starter reward amount for the suggested next paid task. |
| post_another_instruction | No | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| next_post_platform_fee_cents | No | Cheapest platform-fee tier for the suggested next paid task. |
TDQS
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations, the description discloses the critical first-post-free behavior, the live task_url return, and the pending_payment behavior with checkout_url/payment_url on later posts. This is exactly the kind of cost and workflow context an agent needs and is not visible in the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: it states the alias, the invocation trigger, and the payment/response behavior in two sentences. Every sentence contributes useful information with no repetition or filler.
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?
For a simple alias tool with a complete parameter schema, an output schema, and annotations, the description covers the essential behavioral differences between the first and subsequent posts. An agent has enough context to invoke the tool and predict what will happen.
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%, and individual parameters already carry detailed descriptions. The tool description itself adds no new parameter-level detail, so the baseline score of 3 is appropriate; it does not need to compensate for schema gaps.
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 states the tool is an alias for post_task and that its purpose is for the agent to stop guessing and hire a human. It names the resource and the behavior directly, and reading it tells an agent exactly when to invoke it.
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?
The description gives a clear trigger condition ('when the agent should stop guessing and hire a human') and points to the underlying post_task tool. It does not explicitly contrast with the sibling post_human_task, but the alias reference makes the intent sufficiently clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_human_taskPost human task (alias)AInspect
Alias for post_task. Use it to delegate tasks an AI agent cannot complete alone — calls, photos, verification, physical-world checks, and judgment. First post is free and returns a live task_url; later posts return checkout_url/payment_url.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. | |
| category | No | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. | |
| description | Yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. | |
| reward_cents | Yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. | |
| contact_email | Yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| paid | No | True when the task is already treated as paid/open. |
| status | Yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| message | No | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| task_id | Yes | Invoke task identifier. |
| task_url | No | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
| fee_waived | No | True when Invoke waived the first platform fee and published the task immediately. |
| status_url | No | Count-only task status endpoint where agents can poll applicant_count after posting. |
| payment_url | No | Alias for checkout_url for later posts only. |
| checkout_url | No | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| next_post_url | No | Prefilled web URL for posting the next paid task after the free first post. |
| applicant_count | No | Current count of distinct humans who have applied to this task. |
| someone_applied | No | True when applicant_count is greater than zero. |
| platform_fee_cents | Yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| next_post_checkout_url | No | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_reward_cents | No | Cheapest starter reward amount for the suggested next paid task. |
| post_another_instruction | No | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| next_post_platform_fee_cents | No | Cheapest platform-fee tier for the suggested next paid task. |
TDQS
A4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses important behavioral details beyond the annotations: first post is free, returns a live task_url, and later posts return checkout_url/payment_url. This gives an agent meaningful expectations about cost and response behavior, which is especially useful because this is a real-world side-effecting operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no filler. It covers alias status, intended use, examples, and behavioral outcome. Each sentence contributes necessary information and the description is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete enough to call the tool correctly: it explains purpose, how the result URL differs between first and later posts, and relies on a rich schema for parameter details. It is only somewhat limited by not clarifying how this tool relates to hire_human or when an agent should prefer one over the other.
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?
The input schema has 100% description coverage, so all parameters are already documented clearly. The tool description adds some product context, such as free first posting and payment behavior, but it does not add significant parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete purpose: "post_human_task" delegates tasks an AI agent cannot complete alone, with a clear list of examples. It also identifies itself as an alias for post_task, which helps an agent group it with the right sibling. It does not explicitly distinguish itself from hire_human, so it misses top marks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is a clear usage context: use it when an AI agent cannot complete a task alone and a human is needed. However, the description does not explain when not to use it, does not cover selection between hire_human and post_task, and only indirectly implies limits through the examples.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_taskDelegate to a human (first post free)AInspect
Call this when your AI agent is stuck on work software cannot do: phone calls, real-world photos, local pickup/checks, human judgment, verification, QA, or physical presence. Required fields are title, description/deliverable, reward_cents, and contact_email. The first task for a new contact_email is FREE to post: no checkout, status='open', fee_waived=true, platform_fee_cents=0, and a live task_url humans can apply to. Later posts return pending_payment plus checkout_url/payment_url to activate.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. | |
| category | No | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. | |
| description | Yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. | |
| reward_cents | Yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. | |
| contact_email | Yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| paid | No | True when the task is already treated as paid/open. |
| status | Yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| message | No | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| task_id | Yes | Invoke task identifier. |
| task_url | No | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
| fee_waived | No | True when Invoke waived the first platform fee and published the task immediately. |
| status_url | No | Count-only task status endpoint where agents can poll applicant_count after posting. |
| payment_url | No | Alias for checkout_url for later posts only. |
| checkout_url | No | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| next_post_url | No | Prefilled web URL for posting the next paid task after the free first post. |
| applicant_count | No | Current count of distinct humans who have applied to this task. |
| someone_applied | No | True when applicant_count is greater than zero. |
| platform_fee_cents | Yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| next_post_checkout_url | No | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_reward_cents | No | Cheapest starter reward amount for the suggested next paid task. |
| post_another_instruction | No | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| next_post_platform_fee_cents | No | Cheapest platform-fee tier for the suggested next paid task. |
TDQS
A4.3/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Even though annotations already indicate read behavior is mutable and not idempotent, the description goes further by explaining the first-post-per-email free path, status transitions, fee waivers, and checkout/payment URLs. This is highly useful behavioral detail that structured annotations alone do not capture.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded: trigger condition first, then required fields, then free-post behavior and later activation flow. Every sentence adds necessary information, and there is no filler or repetition.
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?
For a tool with only 5 parameters, an output schema, and no nested objects, the description fully covers field requirements, eligibility logic, statuses, and activation flow. Nothing important is missing for an agent to decide on and invoke the call 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 the baseline is 3. The description reinforces which fields are required and communicates that contact_email drives the first-post-free rule, but it does not add substantial parameter-level meaning beyond what the schema already documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly indicates the tool's purpose: delegating software-solvable-inadequate work to humans and posting a task. It states concrete examples of when to use it, such as phone calls and real-world photos, but it does not explicitly distinguish post_task from the sibling tools hire_human and post_human_task.
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?
The description gives an explicit, actionable trigger condition: call this when the AI agent is stuck on work software cannot do. It effectively says when-not to use it by restricting to things software cannot do, but it does not name alternatives or provide explicit exclusions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- Changed
hire_human3 fields changed- added
Output schema / properties / applicant_countAdded value: +{ + "description": "Current count of distinct humans who have applied to this task.", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / someone_appliedAdded value: +{ + "description": "True when applicant_count is greater than zero.", + "type": "boolean" +} - added
Output schema / properties / status_urlAdded value: +{ + "description": "Count-only task status endpoint where agents can poll applicant_count after posting.", + "format": "uri", + "type": "string" +}
- Changed
post_human_task3 fields changed- added
Output schema / properties / applicant_countAdded value: +{ + "description": "Current count of distinct humans who have applied to this task.", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / someone_appliedAdded value: +{ + "description": "True when applicant_count is greater than zero.", + "type": "boolean" +} - added
Output schema / properties / status_urlAdded value: +{ + "description": "Count-only task status endpoint where agents can poll applicant_count after posting.", + "format": "uri", + "type": "string" +}
- Changed
post_task3 fields changed- added
Output schema / properties / applicant_countAdded value: +{ + "description": "Current count of distinct humans who have applied to this task.", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / someone_appliedAdded value: +{ + "description": "True when applicant_count is greater than zero.", + "type": "boolean" +} - added
Output schema / properties / status_urlAdded value: +{ + "description": "Count-only task status endpoint where agents can poll applicant_count after posting.", + "format": "uri", + "type": "string" +}
3 tool updates
- Changed
hire_human5 fields changed- added
Output schema / properties / next_post_checkout_urlAdded value: +{ + "description": "Cheapest one-click platform-fee checkout shortcut for a follow-up paid post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / next_post_platform_fee_centsAdded value: +{ + "description": "Cheapest platform-fee tier for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_reward_centsAdded value: +{ + "description": "Cheapest starter reward amount for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_urlAdded value: +{ + "description": "Prefilled web URL for posting the next paid task after the free first post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / post_another_instructionAdded value: +{ + "description": "Ready-to-relay instruction explaining how to post the next paid task and where to pay.", + "type": "string" +}
- Changed
post_human_task5 fields changed- added
Output schema / properties / next_post_checkout_urlAdded value: +{ + "description": "Cheapest one-click platform-fee checkout shortcut for a follow-up paid post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / next_post_platform_fee_centsAdded value: +{ + "description": "Cheapest platform-fee tier for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_reward_centsAdded value: +{ + "description": "Cheapest starter reward amount for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_urlAdded value: +{ + "description": "Prefilled web URL for posting the next paid task after the free first post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / post_another_instructionAdded value: +{ + "description": "Ready-to-relay instruction explaining how to post the next paid task and where to pay.", + "type": "string" +}
- Changed
post_task5 fields changed- added
Output schema / properties / next_post_checkout_urlAdded value: +{ + "description": "Cheapest one-click platform-fee checkout shortcut for a follow-up paid post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / next_post_platform_fee_centsAdded value: +{ + "description": "Cheapest platform-fee tier for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_reward_centsAdded value: +{ + "description": "Cheapest starter reward amount for the suggested next paid task.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - added
Output schema / properties / next_post_urlAdded value: +{ + "description": "Prefilled web URL for posting the next paid task after the free first post.", + "format": "uri", + "type": "string" +} - added
Output schema / properties / post_another_instructionAdded value: +{ + "description": "Ready-to-relay instruction explaining how to post the next paid task and where to pay.", + "type": "string" +}
3 tool updates
- Changed
hire_human11 fields changed- changed
Input schema / properties / category / descriptionPrevious value: -"Optional category such as research, testing, verification, calls, or physical-world."New value: +"Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." - changed
Input schema / properties / contact_email / descriptionPrevious value: -"Email address where Invoke can contact the task poster."New value: +"Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." - changed
Input schema / properties / description / descriptionPrevious value: -"Detailed instructions for the human worker."New value: +"Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." - changed
Input schema / properties / reward_cents / descriptionPrevious value: -"Worker reward in USD cents. Must be 1000-50000."New value: +"Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." - changed
Input schema / properties / title / descriptionPrevious value: -"Short public title for the human task."New value: +"Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." - changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses."New value: +"Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url." - added
Output schema / properties / messageAdded value: +{ + "description": "Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live.", + "type": "string" +} - changed
Output schema / properties / payment_url / descriptionPrevious value: -"Alias for checkout_url. Present for pending_payment responses."New value: +"Alias for checkout_url for later posts only." - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents. First-post waiver responses return 0."New value: +"Platform fee due before activation, in USD cents. First-post-free responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid."New value: +"Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post." - changed
Output schema / properties / task_url / descriptionPrevious value: -"Live public task URL. Present when the task is opened immediately by the first-post waiver."New value: +"Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user."
- Changed
post_human_task11 fields changed- changed
Input schema / properties / category / descriptionPrevious value: -"Optional category such as research, testing, verification, calls, or physical-world."New value: +"Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." - changed
Input schema / properties / contact_email / descriptionPrevious value: -"Email address where Invoke can contact the task poster."New value: +"Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." - changed
Input schema / properties / description / descriptionPrevious value: -"Detailed instructions for the human worker."New value: +"Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." - changed
Input schema / properties / reward_cents / descriptionPrevious value: -"Worker reward in USD cents. Must be 1000-50000."New value: +"Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." - changed
Input schema / properties / title / descriptionPrevious value: -"Short public title for the human task."New value: +"Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." - changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses."New value: +"Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url." - added
Output schema / properties / messageAdded value: +{ + "description": "Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live.", + "type": "string" +} - changed
Output schema / properties / payment_url / descriptionPrevious value: -"Alias for checkout_url. Present for pending_payment responses."New value: +"Alias for checkout_url for later posts only." - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents. First-post waiver responses return 0."New value: +"Platform fee due before activation, in USD cents. First-post-free responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid."New value: +"Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post." - changed
Output schema / properties / task_url / descriptionPrevious value: -"Live public task URL. Present when the task is opened immediately by the first-post waiver."New value: +"Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user."
- Changed
post_task11 fields changed- changed
Input schema / properties / category / descriptionPrevious value: -"Optional category such as research, testing, verification, calls, or physical-world."New value: +"Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." - changed
Input schema / properties / contact_email / descriptionPrevious value: -"Email address where Invoke can contact the task poster."New value: +"Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." - changed
Input schema / properties / description / descriptionPrevious value: -"Detailed instructions for the human worker."New value: +"Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." - changed
Input schema / properties / reward_cents / descriptionPrevious value: -"Worker reward in USD cents. Must be 1000-50000."New value: +"Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." - changed
Input schema / properties / title / descriptionPrevious value: -"Short public title for the human task."New value: +"Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." - changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses."New value: +"Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url." - added
Output schema / properties / messageAdded value: +{ + "description": "Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live.", + "type": "string" +} - changed
Output schema / properties / payment_url / descriptionPrevious value: -"Alias for checkout_url. Present for pending_payment responses."New value: +"Alias for checkout_url for later posts only." - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents. First-post waiver responses return 0."New value: +"Platform fee due before activation, in USD cents. First-post-free responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid."New value: +"Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post." - changed
Output schema / properties / task_url / descriptionPrevious value: -"Live public task URL. Present when the task is opened immediately by the first-post waiver."New value: +"Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user."
3 tool updates
- Changed
hire_human8 fields changed- changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task."New value: +"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses." - added
Output schema / properties / fee_waivedAdded value: +{ + "description": "True when Invoke waived the first platform fee and published the task immediately.", + "type": "boolean" +} - added
Output schema / properties / paidAdded value: +{ + "description": "True when the task is already treated as paid/open.", + "type": "boolean" +} - added
Output schema / properties / payment_urlAdded value: +{ + "description": "Alias for checkout_url. Present for pending_payment responses.", + "format": "uri", + "type": "string" +} - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents."New value: +"Platform fee due before activation, in USD cents. First-post waiver responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status, typically pending_payment until the checkout is paid."New value: +"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid." - added
Output schema / properties / task_urlAdded value: +{ + "description": "Live public task URL. Present when the task is opened immediately by the first-post waiver.", + "format": "uri", + "type": "string" +} - changed
Output schema / requiredPrevious value: -[ - "task_id", - "status", - "platform_fee_cents", - "checkout_url" -]New value: +[ + "task_id", + "status", + "platform_fee_cents" +]
- Changed
post_human_task8 fields changed- changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task."New value: +"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses." - added
Output schema / properties / fee_waivedAdded value: +{ + "description": "True when Invoke waived the first platform fee and published the task immediately.", + "type": "boolean" +} - added
Output schema / properties / paidAdded value: +{ + "description": "True when the task is already treated as paid/open.", + "type": "boolean" +} - added
Output schema / properties / payment_urlAdded value: +{ + "description": "Alias for checkout_url. Present for pending_payment responses.", + "format": "uri", + "type": "string" +} - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents."New value: +"Platform fee due before activation, in USD cents. First-post waiver responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status, typically pending_payment until the checkout is paid."New value: +"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid." - added
Output schema / properties / task_urlAdded value: +{ + "description": "Live public task URL. Present when the task is opened immediately by the first-post waiver.", + "format": "uri", + "type": "string" +} - changed
Output schema / requiredPrevious value: -[ - "task_id", - "status", - "platform_fee_cents", - "checkout_url" -]New value: +[ + "task_id", + "status", + "platform_fee_cents" +]
- Changed
post_task8 fields changed- changed
Output schema / properties / checkout_url / descriptionPrevious value: -"NanoCorp checkout URL to pay the platform fee and activate the task."New value: +"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses." - added
Output schema / properties / fee_waivedAdded value: +{ + "description": "True when Invoke waived the first platform fee and published the task immediately.", + "type": "boolean" +} - added
Output schema / properties / paidAdded value: +{ + "description": "True when the task is already treated as paid/open.", + "type": "boolean" +} - added
Output schema / properties / payment_urlAdded value: +{ + "description": "Alias for checkout_url. Present for pending_payment responses.", + "format": "uri", + "type": "string" +} - changed
Output schema / properties / platform_fee_cents / descriptionPrevious value: -"Platform fee due before activation, in USD cents."New value: +"Platform fee due before activation, in USD cents. First-post waiver responses return 0." - changed
Output schema / properties / status / descriptionPrevious value: -"Task status, typically pending_payment until the checkout is paid."New value: +"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid." - added
Output schema / properties / task_urlAdded value: +{ + "description": "Live public task URL. Present when the task is opened immediately by the first-post waiver.", + "format": "uri", + "type": "string" +} - changed
Output schema / requiredPrevious value: -[ - "task_id", - "status", - "platform_fee_cents", - "checkout_url" -]New value: +[ + "task_id", + "status", + "platform_fee_cents" +]
1 tool update
- Added
post_task
2 tool updates
- First observed
hire_human - First observed
post_human_task
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Human-as-a-Service for AI agents. Delegate tasks that need a real human, get results via API.
Let your agent hire humans or other agents, and be hired. Post jobs, take bids, pay on completion.
Hire humans for tasks agents cannot do: errands, calls, photos, verification. Escrowed, verified.
API for AI agents to delegate tasks to real humans.
Related MCP Servers
humanforaiofficial
AlicenseAqualityAmaintenanceEnables AI agents to hire real human operators for tasks requiring physical presence, human perception, or judgment, such as verification, testing, data collection, and physical-world tasks.41041MIT- AlicenseAqualityFmaintenanceEnables AI agents to search for and hire humans for real-world tasks.33627MIT
- AlicenseNot gradedqualityCmaintenanceDelegates real-world digital tasks to vetted humans directly from AI chat. Provides tools to get quotes, post tasks, and check status with escrow protection.25MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation1/5
All three tools are aliases for the same post_task operation, so there is no meaningful distinction between them. An agent choosing among hire_human, post_human_task, and post_task is selecting the same action under different names.
Naming Consistency2/5
The names all use a verb_noun shape, but the verbs differ (hire vs post) and the nouns are inconsistent (human, human_task, task). The pattern is not predictable and the names suggest different operations rather than aliases.
Tool Count2/5
Three tools may seem like a reasonable count, but they expose only one underlying operation. The aliases inflate the surface and make the server feel redundant; a single well-named post_task tool would be more appropriate.
Completeness5/5
For the stated domain of posting a task for a human, the operation covers creation, first-post fee waiver, payment flow, and returns a live task URL. Task management such as update or cancel is outside the declared purpose, so no obvious gap exists.