Skip to main content
Glama

ChargerDojo

One OCPI version

chargerdojo_get_ocpi_version
Read-only

Describe one OCPI version: how the credentials token is encoded, whether endpoints split into sender and receiver, which modules are implemented, and what the known limits are. Answers: how does this OCPI version work on the wire.

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

Input Schema

NameRequiredDescriptionDefault
versionYesOCPI version, for example 2.2.1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful return-content context beyond the annotation: credential token encoding, sender/receiver endpoint split, implemented modules, and known limits. With no output schema, this is valuable, though it does not describe the response structure in detail.

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, with the scope front-loaded before the clarifying purpose statement. The final 'Answers:' sentence is somewhat redundant but reinforces the intended use without adding bloat.

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?

For a read-only, one-parameter lookup without an output schema, the description gives the agent enough to understand what information dimensions the tool returns. It is nearly complete; only minor details such as response formatting are absent, and those are unlikely to affect correct invocation.

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%, with an enum and example already documenting the single 'version' parameter. The description adds no additional parameter semantics, constraints, or version-specific guidance, so the baseline 3 is appropriate.

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 ('Describe') and resource ('one OCPI version'), and enumerates the aspects covered: credentials token encoding, endpoint split, implemented modules, and known limits. Sibling differentiation is mostly implicit ('one' vs. compare/list) rather than naming chargerdojo_compare_ocpi_versions or chargerdojo_list_ocpi_versions.

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?

The description frames the use case as answering 'how does this OCPI version work on the wire', which implies a single-version reference lookup. It does not explicitly say when to use compare_ocpi_versions or list_ocpi_versions instead, nor does it state prerequisites or exclusions.

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