Skip to main content
Glama

hire_virtuals_specialist

Destructive

Prepares a zero-custody V1 tender to hire three virtual specialists when V1 creation is enabled; never creates, funds, or signs jobs.

Instructions

[Capability: available_when_deployment_prerequisites_are_met; tier: x402_or_subscription_with_authenticated_session; API: /api/v1/agent/virtuals-acp; authority: /api/v1/agent/status] Deprecated V1 compatibility tool. It prepares a zero-custody V1 tender only when the deployment explicitly enables V1 creation. Prefer prepare_virtuals_tender_v2. This tool never creates, budgets, funds, or signs an ACP job.

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": {
      "sessionId": "<sessionId>",
      "agentAddress": "<agentAddress>",
      "sessionToken": "<sessionToken>",
      "idempotencyKey": "<idempotencyKey>",
      "task": "<task>",
      "simulationId": "<simulationId>",
      "expectedOutputAmount": "<expectedOutputAmount>",
      "expectedGasUsdCents": "<expectedGasUsdCents>",
      "expectedYieldUsdCents": "<expectedYieldUsdCents>",
      "maxPaymentUnits": "<maxPaymentUnits>",
      "providers": "<providers>",
      "approvalNonce": "<approvalNonce>",
      "approvalExpiresAt": "<approvalExpiresAt>"
    },
    "name": "hire_virtuals_specialist"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask payload retained by the local customer connector; FarmDash persists only its commitment hash.
providersYes
sessionIdYes
agentAddressYes
sessionTokenYes
simulationIdYes
approvalNonceYes
idempotencyKeyYes
maxPaymentUnitsYesMaximum total raw Base USDC units (6 decimals) across the three customer-funded jobs.
approvalExpiresAtYes
expectedGasUsdCentsYes
expectedOutputAmountYes
expectedYieldUsdCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by scoping the mutation: despite destructiveHint=true, it clarifies the tool never creates, budgets, funds, or signs an ACP job, and it discloses auth/settlement requirements (x402 or subscription with authenticated session) plus a capability gate. It does not explain what state the prepared tender leaves behind or what the next lifecycle step is, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences with no filler, but it opens with a bracketed metadata prefix (capability/tier/API/authority paths) that is operational plumbing rather than purpose, delaying the key 'deprecated, prefer v2' message. The important deprecation signal should have been first.

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?

For a deprecated compatibility shim, the description covers the essential decision inputs: deprecation, gating condition, the preferred replacement, and the safety scope of what it does not do. Given the shallow schema coverage it could say more about the required approval/session parameters, but the core selection decision is well supported.

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 only 15% across 13 required parameters, including a nested providers object and many cryptographic/approval fields (approvalNonce, approvalExpiresAt, simulationId, idempotencyKey), yet the description explains none of them. It mentions the three customer-funded jobs in passing but adds no meaning beyond the two schema-described fields.

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?

States a concrete verb+resource ("prepares a zero-custody V1 tender") and explicitly corrects the misleading tool name by saying it never creates, budgets, funds, or signs a job. It also names the sibling it is superseded by (prepare_virtuals_tender_v2), so an agent can place it in the lifecycle. Minor ambiguity remains because the name says 'hire' while the behavior is only tender preparation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ("only when the deployment explicitly enables V1 creation") and an explicit alternative ("Prefer prepare_virtuals_tender_v2"). The when-to-use and when-not-to-use conditions are both stated rather than implied.

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

Deploy Server

Other Tools