Skip to main content
Glama

Validate JSON

bursia_json_validate
Read-onlyIdempotent

Check whether a text is valid JSON; returns the error position or the top-level type and size. Pure computation, 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": "bursia_json_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to check, e.g. {"a":1}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / text / description
      Added value: +"The text to check, e.g. {\"a\":1}."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real value beyond that: it discloses the return shape (error position, or top-level type and size) and that the call is free/pure computation, which no structured field states.

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

Conciseness5/5

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

One semicolon-joined sentence that front-loads the purpose and then the return behavior, with a closing note on cost. No filler sentences.

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?

With no output schema, the description correctly compensates by sketching the two possible return branches, and annotations cover the safety profile. Minor gap: 'size' is left undefined (characters vs. bytes vs. node count), which is the only thing an agent might still need.

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?

There is a single required parameter at 100% schema coverage, and the schema example already illustrates the input format. The description adds nothing about the parameter itself, which is the correct baseline when the schema fully documents it.

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: check whether text is valid JSON. The scope (validation, not parsing/formatting) is inherently distinguishable from siblings like bursia_json_format and bursia_json_diff, though no sibling is named explicitly.

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 only implied — an agent can infer this is the tool for syntax-checking JSON before formatting or parsing. There is no explicit when-to-use statement and no comparison to bursia_json_format or bursia_json_path, so the routing 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.

Resources