Skip to main content
Glama

submit_delegated_job_from_file

Same as submit_delegated_job, but the job input is read from a file on disk by the MCP server and sent peer-to-peer via iroh - the file content never enters the model's output tokens.

Instructions

Same as submit_delegated_job, but the job input is read from a file on disk by the MCP server and sent peer-to-peer via iroh - the file content never enters the model's output tokens. Prefer this over submit_and_pay_job_from_file whenever the capability advertises delegation: that tool pays the full listed price up front, while here the provider pulls from your delegation after delivering - on a METERED card only what the job consumed, never more than the listed price. Requires an ACTIVE delegation to the delegate key the capability advertises (check with get_delegation), a persistent agent, and the iroh addon. Text files reach the skill on stdin; binary files via ELISYM_INPUT_FILE. Pass an optional prompt to send a text instruction alongside the file; it rides inline (encrypted) while the file rides P2P. If max_price_lamports is not set, returns the price - or the range, when metered - for confirmation without publishing anything.

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": {
      "input_path": "<input_path>",
      "provider_npub": "<provider_npub>"
    },
    "name": "submit_delegated_job_from_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoOptional text instruction sent alongside the file (e.g. how to edit an image: "make it night", "add a hat"). It rides inline (NIP-44 encrypted) in the job event while the file travels peer-to-peer via iroh. The single attachment slot holds the file, so the prompt cannot spill to a second transfer - keep it short.
capabilityNogeneral
input_pathYesPath to a regular file whose contents become the job input. Absolute or relative to the MCP server's working directory.
kind_offsetNo
timeout_secsNo
provider_npubYes
allow_outside_cwdNoAllow reading a file outside the MCP server working directory. Off by default - the file content is forwarded to the provider before payment and is invisible in the transcript, so reads are confined to the working dir unless this is set. Sensitive files (secret keys, .env, SSH/keypair, ~/.elisym, /proc) are always refused.
max_price_lamportsNoConfirmation cap in the card asset subunits (USDC has 6 decimals). The advertised price must not exceed it. Omit to get a price confirmation without publishing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.60
    • addedInput schema / properties / max_price_lamports / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_price_lamports / minimum
      Added value: +-9007199254740991
  2. Addedv0.1.44

TDQS

A4.7/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so: it discloses the privacy property (file bytes never enter output tokens), the P2P transport via iroh, metered charging capped at the listed price, how text vs binary inputs are delivered (stdin vs ELISYM_INPUT_FILE), and the dry-run behavior when max_price_lamports is omitted. These are non-obvious traits an agent could not infer from the schema.

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 key differentiator is front-loaded in the first clause and the sibling comparison follows immediately, so the structure serves fast selection. It is dense but long, and the stdin/ELISYM_INPUT_FILE delivery detail is somewhat buried mid-paragraph.

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 an 8-param, no-annotation, no-output-schema mutation-and-payment tool this covers prerequisites, safety implications, payment semantics, and the quoting fallback well. Gaps remain on return contents after publication and on the role of kind_offset and timeout_secs, which no structured field explains.

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?

Schema coverage is 50%, so description must add value, and it does for the critical params: it explains input_path sourcing, that prompt rides inline encrypted while the file goes P2P (and must stay short due to the single attachment slot), and that omitting max_price_lamports yields a price/range quote without publishing. The remaining params (capability, kind_offset, timeout_secs, provider_npub) get no added 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?

The description opens with a precise verb+resource ('job input is read from a file on disk by the MCP server') and explicitly anchors it against both siblings: it is like submit_delegated_job but file-sourced, and it is preferred over submit_and_pay_job_from_file. An agent can distinguish all three tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to prefer this tool ('whenever the capability advertises delegation') and why, contrasting the up-front-payment model of submit_and_pay_job_from_file with post-delivery pull. It also lists the preconditions (active delegation checked via get_delegation, persistent agent, iroh addon) that gate a correct call.

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