Skip to main content
Glama

askacharge.com — EV charging network

by com.askacharge
OverviewDiscussionsAdmin

Arrancar una carga

askacharge_arrancar_carga
Destructive

Arranca una carga en remoto (OCPP RemoteStartTransaction). El cargador debe estar conectado y el id_tag autorizado en la marca. CUIDADO: entrega energía real y genera un cobro.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_tagNoTag RFID autorizado con el que se factura la sesión. Opcional: sin él se usa la tarjeta interna PANEL de la marca
connector_idNoConector, 1 por defecto
charge_point_idYesIdentificador de fábrica del cargador, p. ej. CP001

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id_tag / description
      Previous value: -"Tag RFID autorizado con el que se factura la sesión"New value: +"Tag RFID autorizado con el que se factura la sesión. Opcional: sin él se usa la tarjeta interna PANEL de la marca"
    • changedInput schema / required
      Previous value: -[
-  "charge_point_id",
-  "id_tag"
-]New value: +[
+  "charge_point_id"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / charge_point_id / description
      Added value: +"Identificador de fábrica del cargador, p. ej. CP001"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=true), the description adds crucial behavioral context: 'CUIDADO: entrega energía real y genera un cobro', explaining exactly what the destructive effect is. It also mentions the OCPP RemoteStartTransaction protocol. No contradiction with annotations.

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?

The description is two concise sentences, front-loading the action and protocol, then stating prerequisites and a prominent warning. Every sentence adds value with no redundancy.

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 3-parameter tool with fully described schema and rich annotations, the description is complete: it covers the action, preconditions, and consequences. No output schema exists, so return values need not be documented. Minor gap: it does not mention what a successful response looks like, but that is not essential here.

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% – all three parameters have detailed descriptions, including the optional id_tag and its default. The tool description itself does not add extra parameter-level meaning beyond what the schema already provides, so the 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?

The description clearly states the verb and resource: 'Arranca una carga en remoto (OCPP RemoteStartTransaction)'. It specifies the action, the protocol, and is easily distinguished from the sibling tool 'askacharge_parar_carga' by the opposite verb.

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 description provides clear usage prerequisites: 'El cargador debe estar conectado y el id_tag autorizado en la marca' and a strong caution about real energy delivery and billing. It implies when not to use (e.g., if charger is disconnected), though it does not explicitly name the alternative stopping tool.

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

All askacharge.com — EV charging network 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