Skip to main content
Glama
Sign In

ChargerDojo

by com.chargerdojo
OverviewDiscussionsAdmin

Checks for one module

chargerdojo_list_checks
Read-only

List the checks a conformance run of one OCPI module grades at one version: each check id, what it sends, each rule as required or optional with its strength, and the clause of the OCPI spec each rule is graded against, quoted. Answers: what will ChargerDojo hold my module to, and where does the spec say so.

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>",
      "module": "<module>"
    },
    "name": "chargerdojo_list_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor from a previous call. Omit to start at the first check.
moduleYesThe module, as chargerdojo_list_conformance_suites names it.
versionYesThe OCPI version, for example 2.2.1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and with no output schema the description usefully discloses the shape of the return: per-check id, payload, rule requirement/strength, and a quoted spec clause for each rule. That is real added context beyond the annotations. It omits pagination behavior, even though the after cursor implies paged results.

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?

Two sentences, front-loaded with the verb and resource, followed by a compact enumeration of return fields that maps to the tool's value. Dense but every clause contributes; only the rhetorical "Answers:" sentence borders on redundant framing.

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?

With no output schema, the description carries the burden of describing return values and does so field by field, including the quoted spec clause, which is the tool's real differentiator. Combined with full schema coverage and a readOnly annotation, an agent has enough to call this correctly.

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% and both enums are documented, so baseline is 3. The description reinforces that module and version jointly select the graded check set, but it adds no syntax or constraint detail the schema does not already carry.

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 verb and resource: list the checks that a conformance run grades for one OCPI module at one version. The colon-delimited enumeration of what each check contains (id, payload sent, rule required/optional with strength, quoted spec clause) makes the scope unmistakable. It does not name a sibling such as chargerdojo_get_run_checks, so the static-catalog vs. run-results distinction has to be inferred.

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?

"Answers: what will ChargerDojo hold my module to, and where does the spec say so" implies a pre-run inspection use case but never states when to use this versus chargerdojo_get_run_checks or chargerdojo_list_conformance_suites. The only workflow hint, that module is named as chargerdojo_list_conformance_suites names it, lives in the schema rather than the description.

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

All ChargerDojo toolsInspect
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