Skip to main content
Glama

ARL Protocol

arl_prepare_funding

Step 2 of opening a task: for the jobId created in step 1, returns the unsigned configure, setBudget, approve and fund transactions, in order, for the client wallet. Pass the same arguments as arl_prepare_job.

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": "<task>",
      "taskUri": "<taskUri>",
      "client": "<client>",
      "provider": "<provider>",
      "committee": "<committee>",
      "jobId": "<jobId>"
    },
    "name": "arl_prepare_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesAn arl-task/1 document (spec/arl-task/v0.1.0 in github.com/armanalabsai/arlcoin.io)
jobIdYesJob id, decimal
clientYesThe user's wallet: it signs and pays
policyNoThe arl-policy/1 document the task names; omit for a built-in policy
taskUriYeshttps or ipfs URI where validators fetch the task document
providerYesThe agent or service doing the work
committeeYesStaked validators, as many as the task's committee_size

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does make the key disclosure: the output is unsigned transactions in a defined order, so nothing is submitted and signing remains with the client wallet. It says nothing about error conditions (invalid/unknown jobId), idempotency, or what the agent is expected to do with the returned transactions.

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?

Two sentences, front-loaded with the pipeline position, then the returned artifacts and argument rule. No redundant restatement of the name or schema.

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?

For a 7-parameter tool with a nested task document and no output schema, the description usefully compensates by enumerating the returned transactions and their order. Remaining gaps are the return shape (array vs. object) and edge-case behavior, which keep it short of full completeness.

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

Parameters3/5

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

Schema coverage is 100% and every parameter is documented in the schema, so the baseline applies. The line 'Pass the same arguments as arl_prepare_job' adds a useful cross-reference for the six required arguments but clarifies no individual field's meaning beyond 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?

States a specific verb and outcome ('returns the unsigned configure, setBudget, approve and fund transactions, in order') tied to a specific resource (the task-funding step for a jobId). It also positions itself as step 2 of a pipeline, which makes it immediately distinguishable from arl_prepare_job.

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?

Explicitly frames the tool as the second step and names the prerequisite ('for the jobId created in step 1'), so the agent knows arl_prepare_job must run first. It doesn't state what to do on failures or whether it can be re-run, so there is no true when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources