Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Diagnose supplied failure symptoms

diagnose_failure
Read-onlyIdempotent

Generate bounded evidence-class hypotheses and differentiating experiments from supplied symptoms and logs, without exposing raw logs or claiming a root cause.

Instructions

Return bounded evidence-class hypotheses and differentiating experiments for supplied symptoms/logs. Does not expose raw logs or claim a root cause.

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": {
      "symptoms": "<symptoms>"
    },
    "name": "diagnose_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
logsNo
symptomsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: output is bounded, raw logs are not echoed back, and no definitive root cause is asserted — all important expectations for an agent interpreting the result. It stops short of describing the response structure or any size/rate limits on the returned hypotheses.

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

Conciseness5/5

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

Two short sentences, both load-bearing, with the core capability front-loaded and the limitations stated immediately after. No filler, no restatement of the title.

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?

With no output schema, the description should convey the shape of the returned hypotheses and experiments, and it only gestures at it ('bounded', 'differentiating experiments'). Combined with zero parameter description coverage, an agent knows roughly what the tool does but not how to shape inputs or what to expect back.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description carries the burden and largely fails to. It names 'symptoms/logs' only in passing, giving no guidance on the distinction between the two, no expected format for log excerpts, and no mention of the 3000/8000-character bounds or the 10-character minimum on symptoms.

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?

Uses a specific verb-and-resource statement: returns bounded evidence-class hypotheses plus differentiating experiments for supplied symptoms or logs. It also delimits scope with two explicit negatives (no raw-log exposure, no root-cause claim), which separates it from review or diagnostic-adjacent siblings such as review_code_change. The only weakness is jargon ('evidence-class hypotheses'), which takes a moment to parse.

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 by 'supplied symptoms/logs' — the agent can infer it should call this when it has failure symptoms or log excerpts. But there is no explicit when-to-use versus when-not-to-use guidance, no prerequisites for what makes a good input, and no named alternative for adjacent needs (e.g., full code review or requirements audit).

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