Skip to main content
Glama

JSON key audit: inconsistent casing, odd characters and depth

submit_json_key_audit
Idempotent

Audit the keys in a JSON document: keys that differ only by case, keys containing non-identifier characters, total key count, occurrence frequency and maximum nesting depth. Choose this before generating a schema or code from a JSON sample, to find keys that differ only by case, keys with non-identifier characters, and the document's nesting depth. Do not choose this when you need the document validated against a schema; use json-schema-validation. Example requests: Are the keys in this JSON consistent? | Audit this JSON for casing mistakes before I generate a schema. | How deep is this JSON and what keys does it use?

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_json_key_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds what the audit inspects but says nothing about the operational behavior of this being a submitted, priced job — no mention of quoting, authorization, or what happens to the document. With annotations present the bar is lower, so a 3 is appropriate, but the job-execution semantics remain undisclosed in prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The guidance is front-loaded and the routing advice is efficient, but the second sentence restates the first almost verbatim ('keys that differ only by case, keys with non-identifier characters, and the document's nesting depth'), and the three example requests repeat the same points again. Roughly a third of the text is redundant rather than additive.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a tool with four parameters including a priced-job quote and an authorizing identity, the description never mentions that this submits an authorized job, what a quote_id implies, or whether the call is synchronous. That operational gap is the main incompleteness.

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 75%, with the key 'content' parameter already documented as the input.json text with a byte limit, and quote_id/accepted_price/authorized_by each carrying their own descriptions. The description only refers to 'a JSON document' generically and adds no format, size, or pricing semantics beyond the schema. Baseline 3 fits when the schema carries most of the load.

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?

The first sentence gives a specific verb and resource ('Audit the keys in a JSON document') and enumerates exactly what is reported: case-collisions, non-identifier characters, key count, frequency, and max nesting depth. It also names the sibling it is not ('use json-schema-validation'), so an agent can route without opening either schema.

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?

Explicit positive condition ('Choose this before generating a schema or code from a JSON sample') and an explicit exclusion with a named alternative ('Do not choose this when you need the document validated against a schema; use json-schema-validation'). Both the when and the when-not are stated outright.

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