Skip to main content
Glama

thanaton_inject_secrets

Injects environment variables and secrets into a running MicroVM sandbox through Firecracker MMDS in under 50µs without rebuilding the SquashFS rootfs.

Instructions

Zero-rebuild environment variable and secret injection via Firecracker MMDS in <50µs without rebuilding the SquashFS rootfs.

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": {
      "sandbox_id": "<sandbox_id>",
      "secrets": "<secrets>"
    },
    "name": "thanaton_inject_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretsYesKey-value map of secrets and environment variables to inject
sandbox_idYesMicroVM sandbox ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/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 load; it does disclose meaningful behavior — runtime injection through MMDS, no image rebuild, sub-50µs latency. It omits critical traits for a mutation tool: whether existing env/secret keys are merged or overwritten, whether injected secrets survive sleep/wake or restart, and any permission requirements.

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?

A single front-loaded sentence with the operation stated first and the performance claim last. The '<50µs' figure is somewhat promotional but does convey latency behavior; nothing is redundant.

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

Completeness3/5

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

For a small two-parameter tool with rich schema coverage, the description covers what the tool does and how it does it. Since there is no output schema, it should say what the call returns (e.g., confirmation of injected keys) and whether the sandbox must already exist and be running; those gaps leave it only adequate.

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%, so both sandbox_id and the nested secrets map are already documented. The description adds no syntax, naming-constraint, or size-limit detail for the key-value map beyond what the schema provides, so the baseline of 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 combination: injecting environment variables and secrets into a sandbox via Firecracker MMDS. The mechanism and 'zero-rebuild' scope make the operation concrete, but the description never contrasts it with the sibling thanaton_manage_env, which an agent could easily confuse with this one.

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

Usage Guidelines2/5

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

No guidance on when to choose this over thanaton_manage_env or thanaton_deploy_code, and no preconditions are stated (must the sandbox be running? must MMDS be enabled?). The only implicit cue is 'without rebuilding the rootfs', which hints at runtime injection but does not frame a decision.

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

Deploy Server

Other Tools