Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Reset Circuit Breaker

reset_circuit_breaker
Idempotent

Resume operations the server paused after repeated failures. Use it after fixing the cause when a tool returns circuit_open, so calls are allowed through again before the timeout.

Instructions

Let calls through again to operations the server paused after repeated failures.

Use it when a tool returns error_type: circuit_open and you have fixed what made the calls fail (a missing sketch, a wrong reference): without a reset, the operation stays paused until its timeout. Resetting does not fix the cause; a call that fails again counts towards a new pause. Changes: only the server's own state; no SolidWorks document is touched. Returns: data with reset, the operations that were paused (empty when none were).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset_circuit_breaker"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoOptional: `operation` resets only that operation; leave it out to reset every one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description goes further by specifying the scope of side effects ('only the server's own state; no SolidWorks document is touched') and the retry semantics ('a call that fails again counts towards a new pause'). That is exactly the context annotations cannot convey, and nothing in it contradicts the hints.

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?

The what and the when are front-loaded, and the 'Changes:'/'Returns:' labeling keeps the rest scannable. The returns sentence is mildly redundant given an output schema exists, but it is short and does not crowd out the operational guidance.

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?

For a zero-required-parameter state-reset tool, the definition covers purpose, trigger, side-effect scope, failure semantics, and result shape — everything needed to call it correctly and to avoid calling it as a fix-all. The output schema handles return detail, so nothing material is missing.

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 already explains that omitting `operation` resets every operation. The description only echoes that ('the operations that were paused (empty when none were)') in its return note, adding no new meaning about the single parameter, 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 opening sentence states a specific action and resource: it un-pauses ('lets calls through again') operations the server paused after repeated failures. This is a distinct maintenance operation, easily separable from the sibling geometry/document tools, none of which touch circuit state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the exact trigger condition ('when a tool returns `error_type: circuit_open`') plus the prerequisite ('you have fixed what made the calls fail'), and explains the consequence of not calling it ('stays paused until its timeout'). It also pre-empts misuse by stating 'Resetting does not fix the cause', which tells the agent this is not a retry mechanism.

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