Skip to main content
Glama

recycle

Queue a recycling job: consume a recipe's outputs to recover a fraction of its inputs (Must be docked at a base with a recycler facility (auto-routed with preset "fast" by default: the soonest-finishing recycler across your own, your faction's, and ALLIED-granted ones (free to you, but queued at external priority), ownership only breaking ties; or pass facility_id, plus optional "cheap" to pick the lowest fee you would actually pay (your own and your faction's recyclers are free to you, so they always win), or "prefer_own" to keep the job on your own/faction/ally-granted recycler; "workshop" doesn't apply — recycling always needs a real recycler facility). 'quantity' is the number of the recipe's output items to feed in and break down, rounded up to whole recycling runs. Escrows those OUTPUT items from your station storage and returns a lossy fraction of its inputs over subsequent ticks (you get a 'crafting_update' notification each tick recovered inputs land in storage). Recycling is always a net loss by design. Use deliver_to=faction for faction storage. COST CHECK: add dry_run=true for a quote (feedstock consumed, fees, venue, ETA) without queuing anything (not supported with bulk jobs). BULK: pass jobs=[{recipe_id, quantity, facility_id?, preset?, deliver_to?, source?}, ...] to recycle many recipes in one action (up to 50) — each entry is processed independently with per-job success/failure. CANCEL: pass job_id= to cancel a queued job and refund its unconsumed feedstock and fees. Pass job_ids=[...] to cancel several at once. RETARGET: pass job_id= with deliver_to=<...> to redirect a queued job's remaining recovered materials to a different store at the same station instead of cancelling it — nothing else about the job changes.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsNoBulk mode: recycle many recipes in one action. Each entry: {recipe_id, quantity, facility_id?, preset?, deliver_to?, source?}. When set, top-level recipe_id/quantity are ignored; each job is processed independently (partial success). Max 50.
actionNoUse action='cancel' to cancel the queued job named by job_id (passing a bare job_id implies cancel too), or action='retarget' to send the job named by job_id somewhere else (job_id + deliver_to implies retarget too).
job_idNoAct on this queued job instead of recycling. job_id alone cancels it (refunding its unconsumed escrow); job_id together with deliver_to instead redirects the job's REMAINING output to that destination, keeping everything else about the job unchanged.
presetNoAuto-routing preset. 'fast' (default) picks the soonest finish across your own, faction, and ally-granted recyclers; ownership only breaks ties. 'cheap' picks the lowest fee you would actually pay — your own and your faction's recyclers are free to you, so they always win. 'prefer_own' keeps the job on your own (then faction, then ally-granted) recycler whenever one can run it. 'workshop' doesn't apply — recycling always needs a real recycler facility.
sourceNoWhere feedstock (and labor/rental credits) are pulled FROM. Same values as deliver_to. Defaults to deliver_to.
dry_runNoReturn a cost+time quote (feedstock consumed, fees, venue, ETA) without queuing anything. Not supported with bulk jobs.
job_idsNoBulk cancel: cancel many queued jobs in one action. Each ID is cancelled independently with per-job success/failure, so one bad ID doesn't sink the batch. Refunds the unconsumed escrow of every cancelled job.
quantityNoNumber of the recipe's output items to feed in and break down (default 1). Rounded up to a whole number of recycling runs.
recipe_idNoRecipe ID to recycle (the recycler consumes the recipe's outputs and returns a lossy fraction of its inputs). Use catalog with type=recipes to browse.
deliver_toNoOutput destination: 'storage' (default), 'faction' (faction main store — requires manage treasury permission), or 'faction:<bucket name or id>' for a specific Storage Extension bucket. Pass it alongside job_id to redirect an ALREADY QUEUED job's remaining output there instead of queuing anything new.
session_idYesYour session ID from login/register
facility_idNoRoute to a specific recycler facility ID (overrides auto-selection).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / preset / description
      Previous value: -"Auto-routing preset: 'fast' (fewest ticks, default) picks the best eligible recycler globally, so a busy own recycler may route to an idle public rental. 'cheap' picks the lowest fee you would actually pay — your own and your faction's recyclers are free to you, so they always win. Use 'prefer_own' to keep the job on your own (then faction, then ally-granted) recycler whenever one can run it. Auto-routing otherwise prefers your own recycler, then your faction's, then one an allied faction has granted you access to (free to you, but queued at external priority). 'workshop' doesn't apply — recycling always needs a real recycler facility."New value: +"Auto-routing preset. 'fast' (default) picks the soonest finish across your own, faction, and ally-granted recyclers; ownership only breaks ties. 'cheap' picks the lowest fee you would actually pay — your own and your faction's recyclers are free to you, so they always win. 'prefer_own' keeps the job on your own (then faction, then ally-granted) recycler whenever one can run it. 'workshop' doesn't apply — recycling always needs a real recycler facility."
  2. Added
  3. Removed
  4. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Use action='cancel' to cancel the queued job named by job_id (passing a bare job_id implies cancel too)."New value: +"Use action='cancel' to cancel the queued job named by job_id (passing a bare job_id implies cancel too), or action='retarget' to send the job named by job_id somewhere else (job_id + deliver_to implies retarget too)."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "cancel"
      -]New value: +[
      +  "cancel",
      +  "retarget"
      +]
    • changedInput schema / properties / deliver_to / description
      Previous value: -"Output destination: 'storage' (default), 'faction' (faction main store — requires manage treasury permission), or 'faction:<bucket name or id>' for a specific Storage Extension bucket."New value: +"Output destination: 'storage' (default), 'faction' (faction main store — requires manage treasury permission), or 'faction:<bucket name or id>' for a specific Storage Extension bucket. Pass it alongside job_id to redirect an ALREADY QUEUED job's remaining output there instead of queuing anything new."
    • changedInput schema / properties / job_id / description
      Previous value: -"Cancel this queued job (refunding its unconsumed escrow) instead of recycling. Setting job_id implies cancel."New value: +"Act on this queued job instead of recycling. job_id alone cancels it (refunding its unconsumed escrow); job_id together with deliver_to instead redirects the job's REMAINING output to that destination, keeping everything else about the job unchanged."
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Despite minimal annotations (readOnlyHint=false), the description discloses rich behavioral traits: escrows output items, returns lossy fraction over subsequent ticks, sends crafting_update notifications, refunds unconsumed feedstock on cancel, retarget semantics, bulk partial success, and dry_run limitations.

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?

Front-loaded with the core action in the first sentence, then systematically covers modes and caveats. The single long paragraph is dense but every detail serves a purpose given the tool's complexity (12 parameters, multiple modes). Minor verbosity but justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the description explains return behavior (tick-based notifications), cost semantics, cancellation/refund, and retarget effects. Given the high parameter count and mode variety, it provides an unusually complete operational picture.

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 100%, so baseline is 3. The description adds value by explaining interactions between parameters (e.g., job_id with deliver_to implies retarget), preset routing logic, source defaulting to deliver_to, and quantity rounding. It does not fully replace the schema but meaningfully augments it.

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 (queue) and resource (recycling job) with clear scope: consume a recipe's outputs to recover a fraction of inputs. Distinguishes from siblings like craft and scrap_ship by specifying recycler facility requirement and net-loss nature.

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?

Explicitly states prerequisites (must be docked at base with recycler), explains auto-routing presets with conditions, and provides clear when-to-use guidance for dry_run, bulk, cancel, and retarget modes. No ambiguity about alternatives within the tool.

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