ChargerDojo

Validate an OCPI object

chargerdojo_validate_payload

Read-only

Check one OCPI object, sent as JSON text, against the schema ChargerDojo grades that object with at one OCPI version, and list each field that breaks it. The JSON leaves your machine and is sent to chargerdojo.com; it is not stored or logged. Up to 64 KB, 30 calls a minute. Answers: is this a valid OCPI object at my version.

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": {
      "version": "<version>",
      "object": "<object>",
      "json": "<json>"
    },
    "name": "chargerdojo_validate_payload"
  }
}

Input Schema

Name	Required	Description
`json`	Yes	The object itself as JSON text, without the response envelope.
`object`	Yes	Which OCPI object the JSON is, for example token or session.
`version`	Yes	The OCPI version, for example 2.2.1.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond annotations: discloses that JSON leaves the machine and is sent to chargerdojo.com, that it is not stored or logged, plus a 64 KB size cap and 30 calls/minute rate limit. This is exactly the extra context readOnlyHint/openWorldHint cannot convey, and nothing contradicts those hints.

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?

Three tight sentences: purpose, privacy/limits, and the question it answers. Front-loaded with the core action and no filler.

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

Completeness5/5

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

No output schema exists, yet the description explains what comes back (each breaking field listed), along with payload constraints and privacy posture. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% with enums and per-parameter descriptions, so the schema already carries the semantics. The description adds only marginal framing ('one OCPI version', 'JSON text') and the 64 KB limit, which the schema's maxLength already encodes. Baseline 3 applies.

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?

Specific verb and resource: 'Check one OCPI object, sent as JSON text, against the schema... and list each field that breaks it.' No sibling tool performs validation, and the outcome (per-field violations) is stated, so an agent can identify it unambiguously.

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?

The closing line 'Answers: is this a valid OCPI object at my version' gives a clear use case, and the version/object parameters imply context. However, it does not explicitly state when to prefer this over adjacent tools like chargerdojo_list_checks or the comparison tools, leaving routing to inference.

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

All ChargerDojo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?