AlpineLead OI

Field Agents: fund paid Nexus task

fund_field_agent_task

Prepare a real funding route for a Nexus Field Agent task. Prefer MPP for autonomous agents. The Field Agent will not claim or execute until Stripe confirms real payment.

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": {
      "task_id": "<task_id>"
    },
    "name": "fund_field_agent_task"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	mpp for native HTTP 402 machine payment, payment_intent for programmatic Stripe payment, or checkout for a hosted payment link.	mpp
`email`	No	Optional payer email for hosted checkout.
`task_id`	Yes	Nexus task id to fund.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / mode / default

Previous value: -"payment_intent"New value: +"mpp"

changedInput schema / properties / mode / description

Previous value: -"payment_intent for programmatic Stripe payment, or checkout for a hosted payment link."New value: +"mpp for native HTTP 402 machine payment, payment_intent for programmatic Stripe payment, or checkout for a hosted payment link."

AddedSep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate the tool is not read-only and not idempotent, but the description adds important context beyond that: it prepares a real funding route, prefers MPP mode, and states that the Field Agent will not claim or execute until Stripe confirms real payment. This meaningfully clarifies side effects and preconditions.

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 only two sentences long, starts with the core purpose, and includes the most critical behavioral caveat right after. Every sentence earns its place with no repetition of schema or annotation information.

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 high schema coverage, the presence of an output schema, and the annotation set, the description covers the essential operational context: what the tool does, which mode to prefer, and when the Field Agent will act. It does not elaborate on Stripe confirmation handling, but that is not required for correct invocation.

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?

The schema already covers all three parameters with clear descriptions, so the baseline is 3. The description adds extra parameter-level guidance by recommending MPP for autonomous agents, which reinforces and adds context to the default mode value beyond what the schema states.

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 clearly states a specific action ('Prepare a real funding route') and a specific resource ('a Nexus Field Agent task'). It also adds clarifying behavioral context (payment must confirm via Stripe before the Field Agent claims or executes), which makes the tool's role distinct from payment quote or status-checking siblings.

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?

The description gives one useful usage hint: 'Prefer MPP for autonomous agents,' which helps select among payment modes. However, it does not explicitly explain when to use this tool versus alternatives like field_agent_payment_quote or check_field_agent_payment, leaving some routing decisions to inference.

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

All AlpineLead OI tools Inspect

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

Need Help?