Skip to main content
Glama
Sign In

Hominoport

by org.hominoport
OverviewDiscussionsAdmin

Order a service from the human provider

request_action

Submits a task to the human provider and returns payment details for exactly one flow. Either catalogue_id (a fixed position: technical verdict 250 EUR, infrastructure rescue 450 EUR with a 200 EUR diagnostic first, signed observation in Cyprus from 200 EUR) or service_id with price_eur. escrow (recommended for one-off tasks): USDC is held by Coinbase's immutable AuthCaptureEscrow on Base, the provider captures on completion or voids, and you can reclaim on-chain after the deadline; direct: a transfer against the invoice. The provider is notified at once and answers within 72 hours to reply_to (never published); the provider may decline a task outside the offer before any money moves. Description, deadline and acceptance criteria are stored separately and in full.

Input Schema

NameRequiredDescriptionDefault
assetNoUSDC
payerYesyour EVM address on Base: it signs the escrow authorisation, or it is the only address whose direct transfer pays the invoice
deadlineNowhen it must be done (ISO date or plain words)
reply_toYeshttps URL, email or wallet address for the reply; never published
price_eurNo
requesterNohow to call you
task_daysNoescrow only: days after acceptance until you may reclaim
service_idNo
descriptionYeswhat exactly to do and where
catalogue_idNoa fixed catalogue position from list_services (sets service_id and the price)
payment_flowNoescrow (recommended; USDC only; needs payer): held by AuthCaptureEscrow until completion, reclaimable by you after the deadline; direct: pay the invoice by transferdirect
acceptance_criteriaNohow you will judge the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / catalogue_id
      Added value: +{
+  "description": "a fixed catalogue position from list_services (sets service_id and the price)",
+  "enum": [
+    "verdict",
+    "rescue_diagnostic",
+    "rescue",
+    "observation_limassol",
+    "observation_cyprus"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / payer / description
      Previous value: -"your EVM address that will sign the escrow authorisation (escrow only)"New value: +"your EVM address on Base: it signs the escrow authorisation, or it is the only address whose direct transfer pays the invoice"
    • changedInput schema / required
      Previous value: -[
-  "service_id",
-  "description",
-  "price_eur",
-  "reply_to"
-]New value: +[
+  "description",
+  "reply_to",
+  "payer"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / payment_flow / description
      Previous value: -"direct: pay the invoice by transfer; escrow: USDC held by Coinbase's AuthCaptureEscrow on Base until completion (requires payer)"New value: +"escrow (recommended; USDC only; needs payer): held by AuthCaptureEscrow until completion, reclaimable by you after the deadline; direct: pay the invoice by transfer"
    • changedInput schema / properties / payment_flow / enum
      Previous value: -[
-  "direct",
-  "escrow"
-]New value: +[
+  "escrow",
+  "direct"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / payer
      Added value: +{
+  "description": "your EVM address that will sign the escrow authorisation (escrow only)",
+  "type": "string"
+}
    • addedInput schema / properties / payment_flow
      Added value: +{
+  "default": "direct",
+  "description": "direct: pay the invoice by transfer; escrow: USDC held by Coinbase's AuthCaptureEscrow on Base until completion (requires payer)",
+  "enum": [
+    "direct",
+    "escrow"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / task_days
      Added value: +{
+  "default": 14,
+  "description": "escrow only: days after acceptance until you may reclaim",
+  "maximum": 60,
+  "minimum": 1,
+  "type": "integer"
+}
  4. Changed3 schema fields changed
    • addedInput schema / properties / acceptance_criteria
      Added value: +{
+  "description": "how you will judge the result",
+  "maxLength": 2000,
+  "type": "string"
+}
    • addedInput schema / properties / deadline
      Added value: +{
+  "description": "when it must be done (ISO date or plain words)",
+  "maxLength": 100,
+  "type": "string"
+}
    • changedInput schema / properties / description / description
      Previous value: -"what exactly to do, where, by when, acceptance criteria"New value: +"what exactly to do and where"
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag a non-read-only, open-world, non-idempotent operation, and the description usefully adds the escrow lifecycle (Coinbase AuthCaptureEscrow, capture on completion or void, on-chain reclaim after the deadline), the 72-hour reply window, and the fact that reply_to is never published. However it is silent on the consequence of submitting twice, which is the key risk implied by idempotentHint=false, and does not describe what 'payment details' actually contains. Solid added context but with a material gap for a money-moving mutation.

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 purpose is front-loaded and no sentence is filler, but the catalogue pricing is packed into a single dense parenthetical with semicolons that is harder to parse than a short list. Every element is relevant, so this is compression rather than waste.

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 12-parameter, irreversible payment operation with no output schema, the description covers the payment flows, timing and decline path but omits what the returned 'payment details' look like and the follow-up steps (reporting a payment, submitting an escrow signature, checking status). The workflow around this central tool is only partially implied by sibling names.

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 75%, so the baseline is 3, and the description goes beyond the schema by pricing the catalogue positions (verdict 250 EUR, rescue 450 EUR with a 200 EUR diagnostic first, Cyprus observation from 200 EUR) and clarifying that catalogue_id sets both service_id and price. It adds little on asset, requester, or the escrow-only nature of task_days beyond what the schema already states.

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 gives a specific verb and resource — 'submits a task to the human provider and returns payment details for exactly one flow' — and explains the two pathways (catalogue_id, or service_id with price_eur). It does not name a sibling tool to contrast against, so an agent must infer the boundary with get_quote or list_services.

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 explicitly recommends escrow for one-off tasks and explains the direct alternative, plus states the provider may decline a task outside the offer before any money moves. It does not say when to prefer this over get_quote (the obvious upstream step), leaving a workflow gap.

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

All Hominoport 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