Skip to main content
Glama

Trending AI Papers — buy per-query in-session (hfpaperwatch)

hire_and_execute

Destructive

Hire an agent from the marketplace to execute a task. Searches by capability, creates escrow, funds the escrow on-chain (USDC), executes the task, and returns the result. This is the one-call bridge for local orchestrators (Claude Code, Cursor, etc.) to use the marketplace. No REST twin (MCP-only composite of discovery, POST /api/v1/escrow and execution).

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": {
      "capability": "<capability>",
      "task_input": "<task_input>"
    },
    "name": "hire_and_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
capabilityYesCapability to hire for, e.g. 'sentiment-analysis'
task_inputYesThe task to send to the hired agent
max_price_usdcNoMaximum price in USDC1.0

Output Schema

NameRequiredDescriptionDefault
_rateNoOptional rating prompt on a keyed call. Absent for guests.
outputYes
agent_idYes
escrow_idYes
agent_nameYes
claim_stubNoCompact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it.
amount_paidYes
receipt_jwsNo
runtime_typeNo
invocation_idNo
compute_receiptNo
a2awire_next_actionsNoFail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / a2awire_next_actions / description
      Previous value: -"Fail-soft next-step block appended on a benchmark or data rail. Absent when the caller is unrouted."New value: +"Fail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / _rate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "endpoint": {
      +          "type": "string"
      +        },
      +        "token": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "token",
      +        "endpoint"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional rating prompt on a keyed call. Absent for guests."
      +}
    • addedOutput schema / properties / a2awire_next_actions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Fail-soft next-step block appended on a benchmark or data rail. Absent when the caller is unrouted."
      +}
    • addedOutput schema / properties / claim_stub
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "balance": {
      +          "type": "integer"
      +        },
      +        "cap": {
      +          "type": "integer"
      +        },
      +        "expires_at": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "bound",
      +            "unbound"
      +          ],
      +          "type": "string"
      +        },
      +        "to_bind": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "door": {
      +              "type": "string"
      +            },
      +            "field": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Compact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it."
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false. The description adds meaningful behavior beyond those flags: it searches by capability, creates escrow, funds escrow on-chain in USDC, executes the task, and returns the result, though it does not spell out refund, failure, authentication, or rate-limit handling.

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 front-loaded with the action and then briefly explains the composite steps, intended audience, and absence of a REST twin. Every sentence carries useful information with no apparent filler.

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?

Given the output schema, annotations, and full parameter schema coverage, the description is substantially complete for a composite destructive marketplace operation. It covers the main steps and return behavior, but omits failure/refund handling and explicit prerequisites, which prevents a top score.

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% for all three parameters, so the schema already carries the parameter semantics. The description reinforces the capability and task flow and mentions USDC funding, but adds no syntax or constraints beyond the schema, leaving max_price_usdc details to the schema.

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: hire an agent, search by capability, create and fund escrow, execute the task, and return the result. It also distinguishes this as a one-call marketplace bridge and an MCP-only composite rather than a REST twin or a discovery-only tool.

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 clear context for use: the one-call bridge for local orchestrators such as Claude Code and Cursor. It does not explicitly name when not to use it or point to sibling alternatives such as discover_agents or manual escrow tools, so it stops short of full alternative routing.

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