Skip to main content
Glama

ARL Protocol

arl_check_task

Validate an arl-task/1 task and check it against its arl-policy/1 policy. Returns the task hash, the hash committed on chain, and the policy verdict. Reads nothing from the chain.

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>"
    },
    "name": "arl_check_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesAn arl-task/1 document (spec/arl-task/v0.1.0 in github.com/armanalabsai/arlcoin.io)
policyNoThe arl-policy/1 document the task names; omit for a built-in policy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does meaningful work: it states the three things returned (task hash, on-chain committed hash, policy verdict) and clarifies that no chain reads occur, which is the key behavioral fact for this tool. It stops short of saying whether an invalid task throws or returns a failing verdict, whether the call has side effects, or how large a task document it accepts.

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?

Three sentences, each carrying distinct information: the operation, the return values, and the no-chain-read constraint. Front-loaded with the verb and zero filler.

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?

No output schema exists, so the description must sketch the return, and it does name all three return components. Given nested object parameters that are fully covered by schema descriptions, the main residual gap is failure-mode behavior (invalid task, policy mismatch), which keeps it at 4 rather than 5.

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 description coverage is 100% — both 'task' and 'policy' are documented in the schema, including the spec pointer and the 'omit for a built-in policy' default. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Validate an arl-task/1 task') plus the additional operation of checking it against an arl-policy/1 policy. The closing clause 'Reads nothing from the chain' implicitly separates it from the chain-reading siblings (arl_get_job, arl_get_job_receipt, etc.), though it never names an alternative explicitly.

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?

Usage is implied by the wording: use it to validate a task document against a policy. The description does tell the agent that the policy is optional, but it gives no explicit when-to-use vs. when-not guidance and does not contrast with arl_check_evidence or the arl_get_* readers.

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