optivise

optidev_debug_helper

Analyze bug descriptions, error messages, and code context to pinpoint and resolve Optimizely issues with targeted debugging guidance.

Instructions

Provides intelligent debugging assistance for Optimizely-related issues

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": {
      "bugDescription": "<bugDescription>"
    },
    "name": "optidev_debug_helper"
  }
}

Input Schema

Name	Required	Description
`codeContext`	No	Optional relevant code snippets
`errorMessages`	No	Optional error messages or stack traces
`bugDescription`	Yes	Description of the bug or issue encountered

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, and the description only says it 'provides intelligent debugging assistance.' It does not disclose what the tool does with the provided inputs, whether it returns suggestions or only analyzes, or whether it is read-only.

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

Conciseness3/5

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

The description is a single, concise sentence, but it is under-specified. The brevity omits important details that would help an agent use the tool effectively, so it reads more like a placeholder than a well-crafted summary.

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, no annotations, and only a generic description, the tool lacks sufficient context. It does not explain what the output looks like, when to invoke it, or how it integrates with the sibling tools, making it incomplete for reliable selection.

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?

The input schema documents all three parameters with descriptions, covering 100% of the parameter semantics. The tool description adds no additional meaning or context beyond what the schema already provides.

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 introduces the tool as providing 'debugging assistance for Optimizely-related issues,' which signals a general purpose. However, the phrase 'intelligent debugging assistance' is vague and does not clearly differentiate it from sibling tools like optidev_code_analyzer or optidev_context_analyzer.

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?

The description offers no guidance on when to use this tool versus the alternatives. It does not mention that it should be used for errors/bugs, nor does it specify situations where another tool would be more appropriate.

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

Deploy Server