Ailabra Agent Profit Ledger

profit_attest

Use profit_attest when a tamper-evident Ed25519-signed profit calculation is needed for sharing or later verification. Stateless input; price 0.25 USDC. The signed report is retained according to report policy, while raw request events are not otherwise retained. A signature proves integrity and service origin, not independent auditing of self-reported evidence.

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": {
      "events": "<events>"
    },
    "name": "profit_attest"
  }
}

Input Schema

Name	Required	Description	Default
`events`	Yes
`baseCurrency`	No
`exchangeRates`	No
`currentCashBalance`	No
`currentCashBalances`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 29, 2026

TDQS

B3.2/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses stateless input, cost (0.25 USDC), signature mechanism (Ed25519), retention policy (signed report retained, raw events not), and limitation (signature proves integrity, not auditing). This is comprehensive and adds significant value beyond what structured fields could provide.

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

Conciseness4/5

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

The description is three sentences, each serving a distinct purpose: purpose/usage, cost/statelessness, signature/retention. It is well-structured and concise, with no wasted words. However, it could be slightly more structured (e.g., bullet points) but is effective as is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description does not mention what is returned (signed report?). The complex input schema (nested objects, many properties) is not elaborated. Given the high complexity and 0% schema coverage, the description is insufficient for an agent to confidently invoke the tool. More detail on return value and parameter semantics would be needed.

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

Parameters1/5

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

Schema description coverage is 0%, meaning no parameter descriptions in the schema. The description does not explain any of the 5 parameters (events, baseCurrency, exchangeRates, currentCashBalance, currentCashBalances). It mentions 'events' generically but gives no detail on structure or relationships. This is a critical gap.

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 states the tool's purpose: producing a tamper-evident Ed25519-signed profit calculation for sharing or verification. It uses a specific verb (attest) and resource (profit calculation). While it doesn't explicitly differentiate from sibling tools like profit_calculate, the unique signing aspect is implied.

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 opens with 'Use profit_attest when...' providing a clear condition for use. However, it does not specify when not to use this tool or mention alternative tools (e.g., profit_calculate for unsigned calculations). No exclusions are given, but the condition itself is helpful.

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

All Ailabra Agent Profit Ledger 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?