Skip to main content
Glama

env-parse

Env file parse. A .env file body in, URL-encoded as the env query parameter (up to 12,000 bytes), a parsed document out: the vars map with dotenv string values, a convention typing guess per value, the full line and value statistics, and every finding with its line number (malformed lines, invalid keys, duplicate keys, lowercase keys). Price: $0.10 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": {
      "env": "<env>"
    },
    "name": "env-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYesThe .env file body to parse (up to 12,000 bytes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the whole behavioral burden and does most of it: it discloses the $0.10 per-call price, the USDC-on-Base x402 payment flow, the HTTP 402 response with machine-readable terms for unpaid calls, and the byte cap. Missing are rate-limit behavior and whether malformed input errors out versus being reported as findings (only implied by the findings list).

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 sentences, front-loaded with the verb and entirely free of filler; every clause adds information (input contract, output shape, price, payment mechanics). The first sentence is a dense unpunctuated run-on that could be split into a short purpose line plus an output list for faster scanning.

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?

There is no output schema, so the description must describe returns itself -- and it does, naming the vars map, typing guess, statistics, and the four finding categories with line numbers. Combined with the pricing and payment details, an agent has everything needed to call it and interpret the result.

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% and there is a single required parameter, so the baseline is already a 3. The description adds a requirement not in the schema -- that the body must be URL-encoded into the env query parameter -- which is a meaningful calling detail for a body of that size.

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 ('Env file parse') and immediately enumerates the output: vars map with dotenv string values, per-value typing guess, line/value statistics, and line-numbered findings. An agent knows exactly what the tool does and what it returns; nothing here overlaps with csv-convert or json-to-md.

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 rather than stated: the caller supplies a .env body and gets a parsed document. The 12,000-byte cap and URL-encoding requirement narrow the call conditions usefully, but there is no explicit guidance on when to prefer this tool over an alternative or what to do if the input is over the limit.

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