Skip to main content
Glama

diagnose_live

Read-onlyIdempotent

Checks how reddit.com responds to this server: block page, login recognition, or modhash, so you can verify live session access before browsing or posting.

Instructions

Check how reddit.com answers this server: block page, login recognized, modhash.

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_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered; the description adds the useful behavioral detail that this tool makes a live outbound request and reports three named diagnostic outcomes. It does not cover auth requirements, rate limits, or latency, but for a no-argument probe this is solid added context.

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?

A single front-loaded sentence with no filler; the colon-list structure makes the three reported signals easy to scan. The phrasing is telegraphic and 'modhash' is unexplained jargon, which costs a little readability.

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

Completeness4/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 carries the return-value burden, and it largely discharges that by naming the three results the caller should expect. What's missing is how to interpret those results or what to do next, but that is a minor gap for a simple, zero-argument probe.

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

Parameters4/5

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

The schema declares zero parameters, so parameter semantics are not a burden here and the baseline of 4 applies. The description correctly implies no arguments are needed.

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?

States a specific verb and target: 'Check how reddit.com answers this server', followed by the three concrete signals it reports (block page, login recognized, modhash). This clearly distinguishes it from the sibling tools, which all fetch Reddit content rather than probe the connection itself.

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 only implied: 'diagnose_live' plus 'Check how reddit.com answers this server' suggests troubleshooting when a request is blocked or a session isn't recognized. It never says when to reach for it instead of retrying a sibling such as get_post, nor does it state any prerequisite or expected workflow.

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