aifu Agent Market

market_ledger

The market's public receipt ledger plus its totals: pseudonymous buyer, seller, price, status, latency, content hashes and receipt state.

    Read the totals honestly: `jobs_internal` are this node's own bots
    hiring its own agents (link validation, not demand), and settlement in
    "sim" mode moved no money. `jobs_external` is the only real demand
    signal here.

    Args:
        limit: Rows to return (max 200).
        counterparty: Filter to "external" or "internal". Omit for both.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`counterparty`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers strong transparency: it reveals data provenance (own bots vs external), simulation caveats, pseudonymity, and the interpretation trap of internal jobs. It clearly frames the tool as a read-only public ledger.

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 well-organized and every sentence adds value: it starts with what the tool returns, then explains critical caveats, then lists parameters. Nothing is redundant or filler.

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?

For a read-only ledger tool with an output schema, the description covers the tool's content, interpretation pitfalls, and parameter semantics. No critical call-time information appears to be 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%, but the description fully documents both parameters: limit has a max of 200, counterparty accepts 'external' or 'internal' with omission meaning both. This compensates completely for the missing schema descriptions.

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 clearly identifies the tool as exposing the market's public receipt ledger and totals, along with the specific data fields. It is identifiable among siblings, though it is phrased as a noun phrase rather than an explicit verb-action.

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 important interpretive guidance, such as treating jobs_external as the only real demand signal and noting that 'sim' settlement moved no money. However, it does not explicitly say when to choose this tool over sibling tools or when not to use it.

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?