begemot-traffic-light

check_traffic_light

Call this first to activate Begemot reasoning mode and advance the 0→10 step protocol before model inference.

Instructions

ОБЯЗАТЕЛЬНЫЙ ПЕРВЫЙ ВЫЗОВ. Активирует режим Бегемота и делает шаг через дорогу.

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": {
      "request_completed": "<request_completed>"
    },
    "name": "check_traffic_light"
  }
}

Input Schema

Name	Required	Description	Default
`request_completed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv6.4.1Oct 21, 2026

TDQS

D1.3/5.0

Behavior1/5

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

With no annotations, the description carries the full burden, and it discloses nothing usable: 'Behemoth mode' is undefined, 'takes a step across the road' implies a state change with no stated side effects, reversibility, or authorization requirements. The read-flavored name versus the action-flavored description leaves the behavioral contract entirely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the lead sentence is an imperative coercion rather than a purpose statement, and the second sentence conveys no actionable meaning. Brevity here reflects under-specification, not economy.

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

Completeness1/5

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

No annotations, no output schema, an unexplained required parameter, and an undefined mode name leave the definition wholly inadequate. Nothing an agent would need to invoke this correctly — inputs, effects, or result — is present.

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

Parameters1/5

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

There is one required parameter, 'request_completed', with 0% schema description coverage, and the description never mentions it. The agent is given no indication of what value to supply, when, or what it controls — the sole input is undocumented in both structured and unstructured fields.

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

Purpose1/5

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

The name 'check_traffic_light' implies reading a traffic signal state, but the description says it 'activates Behemoth mode and takes a step across the road' — an unrelated action with no defined semantics. An agent cannot tell what this tool actually does, and the name/description mismatch is actively misleading rather than merely vague.

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?

It does assert a usage directive ('MANDATORY FIRST CALL'), which is at least a when-to-use signal, but it is coercive rather than informative: no conditions, no prerequisites, no when-not, and no differentiation from the many siblings (get_begemot_status, traffic_light_history, reset_crossing) that sound related.

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

Deploy Server