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

begemot-traffic-light

by dfvjgjgjg-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

focus_on_task

Directs the coding model to concentrate on a specified task description before inference, keeping reasoning aligned with the requested objective.

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": {
      "task_description": "<task_description>"
    },
    "name": "focus_on_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv6.4.1

TDQS

D1.3/5.0
Behavior1/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 and delivers nothing: no indication of what focusing entails, whether it mutates state, what permissions are needed, or what effect it has on the conversation.

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?

The sentence is short but this is under-specification rather than conciseness; nothing meaningful is front-loaded because nothing substantive is said.

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?

For a tool with a required undocumented parameter, no annotations, and no output schema, the description is entirely inadequate. An agent cannot determine what the tool does or how to invoke it correctly.

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, task_description, with 0% schema description coverage. The description says nothing about what the parameter should contain, its format, or its purpose, so it fails to compensate for the documentation gap.

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

Purpose2/5

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

The description ('Фокусировка на задаче' / 'Focus on the task') is essentially a tautological restatement of the tool name focus_on_task. It conveys no specific verb+resource beyond what the name already says, and does not distinguish it from siblings like reasoning_guard or suppress_refusal.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, or which sibling to prefer. The single sentence offers no context for selection.

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