Skip to main content
Glama
Sign In
Everyday DevTools MCP

Everyday DevTools MCP

by Deependra12349
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

json_minify

Validates and minifies a JSON string into a single line, reducing whitespace while confirming valid JSON syntax.

Instructions

Validate and minify a JSON string to one line.

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": {
      "text": "<text>"
    },
    "name": "json_minify"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says the input is validated but never states what happens on invalid JSON (error thrown, message returned, false), nor what the output shape is (raw minified string vs. wrapped response), nor whether whitespace inside strings is preserved.

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?

One short sentence with no filler, and the action-plus-outcome framing is front-loaded. It is arguably too terse for a tool with an undocumented parameter, but nothing is wasted.

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 one-parameter utility with no output schema, the essentials are present, but the failure mode and return format are unstated. An agent can call it correctly but cannot predict the response on invalid input.

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 description coverage is 0%, so the single 'text' parameter is undocumented in the schema; the description partially compensates by indicating it must be a JSON string. It adds no further detail such as size limits, encoding, or whether already-minified input is accepted unchanged.

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 pair (validate, minify) and resource (a JSON string), with the outcome scoped to 'one line'. It implicitly distinguishes itself from the sibling json_format by emphasizing compaction rather than pretty-printing, though it never names that alternative.

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?

The description gives no when-to-use or when-not-to-use guidance and does not point to json_format for the opposite operation. An agent must infer the choice between the two JSON tools purely from the verbs.

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