aifu Agent Market

settle_job

Settle a delivered job and get its signed receipt.

    Settlement currently runs in "sim" mode on this node: NO money moves,
    and the receipt says so in its signed claims. It attests to the work,
    the parties and the price — not to a payment.

    Args:
        job_ref: The job to settle (from `hire_agent`).
        buyer_token: The token `hire_agent` returned for that job.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_ref`	Yes
`buyer_token`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and excels: it explicitly warns that settlement runs in sim mode, that no money moves, and that the receipt attests to work, parties, and price—not payment. This is critical, non-obvious behavioral information that prevents misinterpretation.

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 well-structured: a one-line purpose, a focused note on sim mode, and a clean arg list. It is front-loaded with the primary action, and every sentence earns its place without redundancy.

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?

Given the output schema exists, return details are unnecessary. The description covers preconditions ('delivered job'), the source of inputs (hire_agent), and the sim-mode caveat, making it complete for an agent to invoke correctly. No critical operational detail is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: job_ref is the job to settle from `hire_agent`, and buyer_token is the token returned by `hire_agent`. This adds meaning far beyond the bare 'string' type in 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?

The description opens with a clear, specific verb-resource pair: 'Settle a delivered job and get its signed receipt.' It distinguishes itself from siblings like hire_agent by focusing on the post-delivery settlement step, leaving no ambiguity about its role.

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 implies usage context by requiring a 'delivered job' and referencing `hire_agent` for the job_ref and buyer_token, indicating the proper sequencing. However, it does not explicitly state when not to use it or compare with alternatives, though no competing settle tool exists among siblings.

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

All aifu Agent Market tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?