Skip to main content
Glama

Diagnose a broken bot (VIP)

diagnose_broken_bot
Read-onlyIdempotent

VIP. Fix My Bot. Takes a symptom in plain words (and work log lines if there are any) and returns the most likely cause, what to check, how to fix it, and when to send it for the optional human review. Without a member token it returns a labeled demo for a common symptom.

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

Input Schema

NameRequiredDescriptionDefault
symptomNoWhat went wrong, in plain words.
log_excerptNoThe last few lines of the work log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the VIP/member-token requirement and the fact that an unauthenticated call degrades to a labeled demo for a common symptom, which an agent could not infer from annotations.

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?

Compact and largely front-loaded, with the output contract spelled out in a single efficient sentence. The leading 'VIP.' and 'Fix My Bot.' fragments are label-like stubs that consume space before the actual purpose statement.

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

Completeness3/5

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

There is no output schema, and the description does enumerate the four return components plus the demo fallback, which helps. However, it never explains the human-review escalation mechanics or how the token gate is supplied, leaving some gaps for a tool with a branching authenticated/demo behavior.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema. The description adds only mild meaning, mainly that log_excerpt is optional and that the symptom should be expressed in plain words, which is close to what the schema already says.

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

Purpose4/5

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

Names a specific verb and resource (diagnose a broken bot) and outlines both what goes in (a plain-word symptom plus optional log lines) and what comes back (likely cause, what to check, how to fix, when to escalate). It does not, however, contrast itself with siblings such as check_safety_rules or analyze_voice_drift, so differentiation is by name alone.

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?

Usage is implied rather than stated: the agent learns to pass a symptom and add work-log lines 'if there are any', and that human review is an optional follow-on. There is no explicit when-to-use versus when-to-use-something-else guidance or statement of prerequisites beyond the member-token note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources