Get the hosted, non-custodial Cherum batch-payout and multi-chain fan-out links (the user signs in their own wallet), with the full fee and risk disclosure.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| fees | Yes | ||
| page | Yes | ||
| risk | Yes | ||
| operator | Yes | ||
| fanoutSend | Yes | ||
| batchPayouts | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "fees": {
+ "properties": {
+ "cherumFeeBps": {
+ "type": "integer"
+ },
+ "note": {
+ "type": "string"
+ },
+ "quietworkFeeBps": {
+ "type": "integer"
+ },
+ "totalBps": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "cherumFeeBps",
+ "quietworkFeeBps",
+ "totalBps",
+ "note"
+ ],
+ "type": "object"
+ }
+ },
+ "properties": {
+ "batchPayouts": {
+ "type": "string"
+ },
+ "fanoutSend": {
+ "type": "string"
+ },
+ "fees": {
+ "$ref": "#/$defs/fees"
+ },
+ "operator": {
+ "type": "string"
+ },
+ "page": {
+ "type": "string"
+ },
+ "risk": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "batchPayouts",
+ "fanoutSend",
+ "page",
+ "fees",
+ "risk",
+ "operator"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden well by disclosing that the links are hosted, non-custodial, require the user to sign in their own wallet, and include full fee and risk disclosure. It still lacks explicit safety-profile details such as read-only behavior, rate limits, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. Each detail—hosted, non-custodial, sign-in requirement, fee/risk disclosure—adds useful meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the empty input schema and the presence of an output schema, the description supplies enough context about what the tool retrieves and the wallet-signing model. The main remaining gap is explicit routing guidance against the sibling tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics because there are none.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb, 'Get,' and a specific resource, 'hosted, non-custodial Cherum batch-payout and multi-chain fan-out links.' It is clear what the tool returns, though it does not explicitly contrast itself with the sibling check_payout_list tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the resource type: call this to obtain payout/fan-out links rather than to check a payout list. However, the description does not explicitly state when to use this tool versus check_payout_list, nor does it give when-not-to-use conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.