Skip to main content
Glama
Sign In
begemot-traffic-light

begemot-traffic-light

by dfvjgjgjg-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_begemot_status

Retrieves the complete status of the Begemot traffic-light system, including current state, health, and configuration, for monitoring and debugging.

Instructions

Получить полный статус бегемота.

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_begemot_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv6.4.1

TDQS

C2.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 carries the full behavioral burden, yet it discloses nothing beyond the bare operation. It does not clarify whether this is a safe read, whether it has side effects, what permissions are required, or what 'full status' encompasses.

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?

A single short sentence with no filler; the operation is front-loaded. It is appropriately sized for a no-argument tool, though it is arguably under-specified rather than concise in a helpful way.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place an agent could learn what the returned 'status' contains, and it says nothing. For an unannotated tool returning an unknown payload about an unexplained entity, this is a significant gap.

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 tool takes zero parameters, so there is nothing for the description to explain at the parameter level and no schema gap to compensate for. The baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('Получить'/get) and a resource ('статус бегемота'/hippo status), so the basic operation is identifiable. However, 'begemot' is an opaque, project-specific entity with no explanation, and 'full status' is vague about what is actually being inspected. It does not distinguish this tool from the sibling begemot_help.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool versus alternatives such as begemot_help or the other sibling tools. The agent must infer usage purely from the name, with no stated context or exclusions.

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