Skip to main content
Glama

Import a JSON document

import_json
Read-only

Parse and normalize a document from a JSON string, reporting why it is invalid when it is.

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": {
      "source": "<source>"
    },
    "name": "import_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that invalid input produces an explanatory error, which is useful beyond the annotations, but it says nothing about what normalization changes (ids, ordering, metadata) nor addresses the non-idempotent hint.

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?

A single sentence, front-loaded with the action and followed by the error-reporting behavior. No redundant or filler wording.

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?

With no output schema, the description should say how a successful parse is reported (inline result, created document, identifier) and how errors surface. It covers the error side but leaves the success side under-specified for an import-type operation.

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 one parameter at 0% schema coverage, so the description must carry the load. Saying the document comes from a 'JSON string' identifies the expected input format, but it gives no detail on size limits, expected document shape, or encoding beyond that.

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?

The description names a specific verb pair (parse and normalize) and a resource (a document from a JSON string). It is clear what the tool does, though it does not explicitly differentiate itself from siblings like import_markdown or validate.

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: the tool is for JSON input and reports reasons for invalidity, suggesting it fits validation/import flows. There is no explicit when-to-use or when-not-to-use guidance, and the presence of sibling tools like import_markdown and validate makes that omission notable.

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