Skip to main content
Glama

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

JSON schema from example: infer a JSON Schema

json_schema
Read-only

Infer a JSON Schema (draft 2020-12) from an example JSON value: types, nested object properties, required keys, array item shapes merged across all items, and string formats (date-time, date, email, uri, uuid). Use to document an API response or to validate later data against the same shape. Example: json={"id":1,"email":"ada@example.com","tags":["a","b"],"created":"2026-10-23T08:00:00Z"}. 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": {
      "json": "<json>"
    },
    "name": "json_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesThe example JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds the cost model the annotations cannot express: $0.01/call via x402 USDC or card key, first 25 free, failed calls free, and explicitly that "each call is charged, so repeats are not free." That last clause directly explains the non-obvious idempotentHint=false annotation, turning a potentially confusing flag into an understandable billing trait.

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 output dialect, then what is inferred, then usage, then a concrete example, then commercial terms. Every sentence carries information, but the closing pricing sentence is long and packs several distinct facts (price, two payment rails, free tier, failure policy, repeat charging) into one block.

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?

There is no output schema, and the description compensates by naming the output artifact and dialect (a draft 2020-12 JSON Schema) plus the facets it will contain. For a one-parameter, read-only tool this covers what an agent needs; only edge-case behavior (empty input, non-object roots, arrays of mixed types) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 baseline is already 3. The description adds real meaning beyond the schema's bare "The example JSON" by showing a literal value (json={"id":1,"email":"ada@example.com",...}), which clarifies that the input is a JSON-encoded string containing an object, not flattened fields. It does not discuss size limits or handling of non-object roots.

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+resource ("Infer a JSON Schema") and enumerates exactly what is inferred: types, nested object properties, required keys, array item merging, and string formats. It also pins the output dialect (draft 2020-12), which no sibling name implies. An agent can distinguish this from json_validate or json_repair on the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete use cases ("document an API response" and "validate later data against the same shape"), which clearly frames the infer-from-example scenario. It stops short of naming alternatives or stating when not to use it (e.g. when the data is already a schema, or when json_validate is the right call), so it lands at a clear-context 4 rather than an explicit routing 5.

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.