Skip to main content
Glama

Caelara Labs Agent Safety

schema_enforcer

Validate and coerce data to a JSON Schema

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": {
      "data": "<data>",
      "schema": "<schema>"
    },
    "name": "schema_enforcer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData to enforce
schemaYesJSON Schema subset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. The word 'coerce' usefully signals that input data may be transformed rather than merely checked, but it says nothing about failure behavior (raise vs. partial result), which schema keywords are supported, or what the response contains.

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 seven-word sentence with both verbs front-loaded and zero filler. Nothing is wasted, though the brevity is as much a limitation as a virtue here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool takes nested objects, has no annotations and no output schema, so the description is the only place return and error semantics could be explained — and it is silent on both. An agent cannot tell whether it receives coerced data, a boolean validation verdict, or a thrown error.

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 100%, so both parameters are already documented in the schema. The description adds no format hints or meaning beyond the schema's own 'Data to enforce' and 'JSON Schema subset' text, which is the expected baseline.

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 pair of verbs (validate and coerce) against a named resource (a JSON Schema), which is concrete enough to act on. It does not distinguish itself from the overlapping sibling json_auto_repair, so an agent must infer whether repair or schema-conformance is the right entry point.

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

Usage Guidelines2/5

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

The description gives no when-to-use context, no prerequisites, and no mention of any alternative tool. With a sibling like json_auto_repair in the catalog, the absence of any routing guidance is a real gap.

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