Skip to main content
Glama
Sign In
Monta MCP Server

Monta MCP Server

by nickknissen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

stop_charge

Stop an active electric vehicle charging session by providing its charge ID. Returns session details or error.

Instructions

Stop an active charging session.

Args:
    charge_id: The ID of the charge session to stop

Returns:
    Charge session details dictionary or error response

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": {
      "charge_id": "<charge_id>"
    },
    "name": "stop_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
charge_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must convey behavioral traits. It mentions stopping an active session and returning either details or an error response. However, it does not disclose prerequisites (e.g., authorization), side effects, or what happens if the charge_id is invalid.

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 extremely concise: one line for purpose, then a clear list of arguments and return values. Every sentence is essential and there is no extraneous information.

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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly complete. It covers the action, argument, and return type. It could be enhanced by clarifying that the charge must be active or by noting potential error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema defines only the type and required status for charge_id. The tool description adds meaning by explaining that it is 'The ID of the charge session to stop'. This is helpful since schema coverage is 0%. However, it lacks guidance on how to obtain the ID or format constraints.

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 tool name 'stop_charge' and description 'Stop an active charging session' clearly indicate the action (stop) and resource (charging session). It is easily distinguished from siblings like 'start_charge' and 'get_charges'.

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 implies the tool should be used to stop currently active charging sessions. It does not explicitly state when not to use it (e.g., if already stopped) or mention alternatives, but the context from sibling names provides enough clarity.

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

Deploy Server

Other Tools