Skip to main content
Glama
Sign In
MaverickMCP

MaverickMCP

by wshobson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_circuit_breaker_status

Check circuit breaker states, failure counts, and performance metrics for all external API connections to monitor system health.

Instructions

Get status of all circuit breakers.

Returns information about circuit breaker states, failure counts, and performance metrics for all external API connections.

Returns: Dictionary containing circuit breaker status information

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": "get_circuit_breaker_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only states what is returned, not side effects, rate limits, or safety (e.g., read-only). The 'get' verb implies read-only, but the description does not explicitly confirm or provide additional behavioral context.

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 description is concise (3 sentences) and front-loaded with the main purpose. The 'Returns:' section is slightly redundant but not harmful. Could be slightly tighter without the Returns section.

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?

Given the tool has no parameters and the output schema exists (though not shown), the description sufficiently explains what the tool does and the general nature of the response. It is complete for a simple status retrieval tool.

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 input schema has zero parameters, so schema description coverage is 100%. The description adds meaning by explaining the return structure (dictionary with status info), which aids understanding. Baseline for 0 params is 4.

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 'Get status of all circuit breakers' with specific verb and resource. It further details the return content (states, failure counts, performance metrics). There is no ambiguity and it distinguishes itself from sibling tools that target different resources.

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 implies the tool is for checking circuit breaker status but provides no explicit guidance on when to use vs alternatives or when not to use. No exclusions or context about alternatives are given.

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