Skip to main content
Glama
read-only-reddit-old

read-only-reddit-old

by Xdabier

status

Verify the read-only-reddit-old browser extension is connected before searching or reading Reddit threads. Does not load any Reddit page.

Instructions

Check that the read-only-reddit-old browser extension is connected. Does not load any Reddit page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It usefully states the tool loads no Reddit page, signaling a cheap, side-effect-free probe with no rate-limit or navigation cost. It does not say what a failure looks like (exception vs. negative result) or whether it verifies the extension version, leaving real behavioral gaps.

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 with zero filler. The core purpose is front-loaded and the non-obvious behavioral constraint follows immediately.

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?

For a trivial zero-parameter probe with no output schema, the description covers intent and the key no-navigation behavior. The one meaningful omission is how connectivity is reported back to the caller, which matters for a status tool but is a small gap given the tool's simplicity.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. Nothing in the description misleads about inputs.

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: check that the read-only-reddit-old browser extension is connected. The clause 'Does not load any Reddit page' distinguishes it from the sibling readers (read_listing, read_thread, search), so an agent will not confuse it with a content fetch. It stops short of stating what the check returns (a boolean, an error, a status string), which keeps it from a 5.

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: an agent can infer this is a pre-flight connectivity probe to run before read_listing/read_thread/search. There is no explicit statement such as 'call this first if a read fails' or any exclusion beyond the note that no page is loaded. Adequate but leaves the when-to-use decision to inference.

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