Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Minify JSON: remove whitespace from JSON to make it compact

json_minify
Read-only

Remove all unnecessary whitespace from JSON and report the size before and after. Use to shrink payloads or prompts. Example: text={ "a" : 1 }. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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
textYesThe JSON text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with "Reads or computes only and changes nothing". It also adds behavior the annotations cannot express: per-call pricing via x402 USDC or card key, 25 free calls, failed calls free, and why repeats are not free — which coherently explains idempotentHint=false. Return shape is only described as size before/after, but that is reasonable.

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 action and the outcome, then the example, then commercial terms. Every sentence carries information, though the pricing clause is dense and slightly crowds out operational guidance.

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 a one-parameter, read-only transform with no output schema, the definition covers action, input example, side effects, cost, and what is reported back. Only explicit sibling routing is missing, which keeps it from a 5.

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% for the single parameter, so the schema already defines `text`. The description's example (`text={ "a" : 1 }`) hints that the input is raw JSON text with whitespace, which is marginal added meaning. Baseline 3 is appropriate given the schema does the heavy lifting.

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 (remove whitespace from JSON) and adds the output behavior (report size before and after), plus an inline example. An agent can distinguish it from json_format or json_repair without opening the schema.

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?

"Use to shrink payloads or prompts" gives an implied usage context, which is enough to know the intent. However, it never names an alternative or a when-not-to-use case (e.g., do not use when the JSON is invalid or when readability/comments must be preserved), so routing between this and json_format is left to inference.

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.