Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_agent_schema_enforcer

Validates and coerces input data to a JSON Schema, helping enforce safe, structured agent outputs.

Instructions

[Agent Safety] Validate and coerce data to a JSON Schema Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://agent.caelaralabs.com.

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": "caelara_agent_schema_enforcer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData to enforce
schemaYesJSON Schema subset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/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 disclosure burden, yet it omits the most important behavior: whether invalid data raises an error, returns a partial result, or is silently coerced. It does add latency figures (p50 11 ms, p95 15 ms) and the backend endpoint, which are genuine extra context, but operational semantics around failure and coercion strictness are absent.

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?

Short and front-loaded on the useful part, but the benchmark statistics and the "Calls https://..." sentence are promotional framing that do not help an agent decide or invoke. Roughly half the text is spent on non-operational claims.

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?

With nested objects, two required parameters, no annotations, and no output schema, the description should explain what a validation call returns and how failures surface. Instead it spends its words on latency and hosting, leaving the return contract entirely undefined.

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 (data, schema) are already documented in the input schema, and the baseline is 3. The description adds no format or syntax detail beyond that, and notably it does not explain which JSON Schema subset is supported even though that constrains callers.

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?

"Validate and coerce data to a JSON Schema" is a specific verb+resource pair that accurately describes the operation. It does not distinguish itself from overlapping siblings such as caelara_agent_json_auto_repair or caelara_agent_agent_output_validator, so an agent cannot route between them from this text alone.

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 or when-not-to-use guidance and names no alternative. An agent learns only that this is an "[Agent Safety]" tool, which is a category label rather than a usage rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools