Skip to main content
Glama
Sign In

ChargerDojo

by com.chargerdojo
OverviewDiscussionsAdmin

Run a journey on an endpoint

chargerdojo_run_journey

Run an OCPI charging journey against an endpoint registered on this account, the sandbox or your own, and return its report id. Against your own endpoint it needs the Integrate plan, and a few journeys need a higher one, which chargerdojo_list_journey_templates names. Answers: does my endpoint pass this journey.

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": {
      "targetId": "<targetId>"
    },
    "name": "chargerdojo_run_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
retryKeyNoA key of your choosing for this run. Calling again with the same key returns the run it started instead of starting another. Omit it to start a new run on every call.
targetIdYesThe registered endpoint to run against, from chargerdojo_list_targets.
templateIdNoJourney to run, from chargerdojo_list_runnable_journeys. Omit to run the shortest one that fits the endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and idempotentHint=false, so the description's real contribution is the plan/entitlement requirement and the fact that a report id comes back. That is value beyond the structured fields, though it omits what the run actually does to the remote endpoint or how to follow up on the report.

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?

Two tight sentences with the action and return value front-loaded, followed by the entitlement caveat and the intent framing. No filler or restatement of the title.

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?

With no output schema, saying it returns a report id covers the return-value gap, and the plan constraint is disclosed. It could go further by pointing to chargerdojo_get_run_verdict or get_run_checks for consuming the report, but nothing essential is missing for a correct call.

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%, and the schema itself documents targetId, retryKey idempotency, and the templateId enum, so the schema does the heavy lifting. The description only adds that some templates require a higher plan, which is marginal extra meaning over the enum list.

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 ('Run an OCPI charging journey against an endpoint') and the return value ('return its report id'), so the action is unmistakable. However, it lists 'the sandbox' as a valid target even though a dedicated sibling chargerdojo_run_sandbox_journey exists, leaving the split between the two slightly blurred.

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?

Gives concrete context for use – an endpoint on your account, plan gating for your own endpoint, and a pointer to chargerdojo_list_journey_templates for journeys needing a higher plan. It also frames the intent ('does my endpoint pass this journey'). It stops short of explicitly saying when to prefer the sandbox sibling instead.

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