Skip to main content
Glama
Sign In

DeAI Artifact Gateway

by io.github.jake-zaiba
OverviewDiscussionsAdmin

Run a verified transform (0.0010)

run_program
Read-only

Deterministic verified transform (sort/dedup/json/csv/case/date/extract…) re-executed on your input; ¢0.1; returns output + receipt. Call match or programs first to find the class.

Input Schema

NameRequiredDescriptionDefault
inputYes
class_idYes
pow_nonceNoNonce such that SHA-256(challenge || ':' || nonce) has difficulty_bits leading zero bits
x_paymentNox402 v2 PaymentPayload, base64 JSON, for the PaymentRequired in the result's `x402.v2.required` (when the USDC rail is open); x402 v1 is not accepted
input_kindNooptional: what the input is (lines, csv, json, numbers, text, …); a kind that does not fit the program's `in` is refused before anything is metered
work_tokenNoWork-rail token (deai_wk_…) earned with the work tool; spends credit on this node. Same as sending Authorization: Bearer.
pow_challengeNoThe challenge from a payment_required result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / x_payment / description
      Previous value: -"x402 v1 PaymentPayload, base64 JSON, for one of `accepts` (when the USDC rail is open)"New value: +"x402 v2 PaymentPayload, base64 JSON, for the PaymentRequired in the result's `x402.v2.required` (when the USDC rail is open); x402 v1 is not accepted"
  2. Changed1 schema field changed
    • changedInput schema / properties / work_token / description
      Previous value: -"Work-rail token (deai_wk_…) earned with work_scout / work_synthesis; spends credit on this node. Same as sending Authorization: Bearer."New value: +"Work-rail token (deai_wk_…) earned with the work tool; spends credit on this node. Same as sending Authorization: Bearer."
  3. Changed1 schema field changed
    • addedInput schema / properties / input_kind
      Added value: +{
+  "description": "optional: what the input is (lines, csv, json, numbers, text, …); a kind that does not fit the program's `in` is refused before anything is metered",
+  "type": "string"
+}
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive/openWorld, and the description adds real context beyond them: deterministic re-execution, a fixed cost (¢0.1), a returned receipt, and refusal of mismatched input kinds before metering. The payment/PoW rails are only alluded to via the schema, so it stops short of full disclosure of cost and failure behavior.

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?

Two tight sentences that front-load what the tool does and where the cost sits, then close with the prerequisite. Slightly telegraphic enumeration ('sort/dedup/json/...'), but every clause carries information.

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-param tool with no output schema, the description still covers the core contract (transform + receipt) and the discovery prerequisite, while schema descriptions cover the payment and work-token params. Metering failure modes and what 'receipt' contains are the remaining gaps.

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

Parameters4/5

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

The two undescribed required params get meaning from the description: class_id is resolved via match/programs, and input is what the program is re-executed on. The payment and proof parameters are already documented in the schema, so only the interaction between class_id and input_kind is left implicit.

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 resource: re-executes a deterministic verified transform (sort/dedup/json/csv/...) on the supplied input, returning output plus a receipt. It also names the class-discovery siblings (match, programs), so an agent can tell it apart from those tools without opening schemas.

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 says 'Call match or programs first to find the class,' which is a concrete prerequisite and points at the alternatives to use beforehand. It does not state when-not-to-use or what happens if the class is wrong, but the routing guidance is clear.

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

All DeAI Artifact Gateway toolsInspect
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