Skip to main content
Glama
sadik004
by sadik004

reddit_auth_status

Verify if your Reddit session is active and retrieve your username, karma, and notification count to confirm access.

Instructions

Verify current Reddit session validity, extracting authenticated username, karma, and notification metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the behavior of verifying session validity and extracting specific metrics, which adds useful context. However, it does not mention side effects, authentication requirements, error behavior, or what happens when the session is invalid.

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?

The description is a single, front-loaded sentence with no filler. It states the action, the target, and the key outputs efficiently.

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 zero-parameter status-check tool, the description is mostly complete: it names the purpose and the returned metrics, and there is no output schema to supplement. It lacks usage context and behavioral caveats, but an agent can likely invoke it correctly with the information given.

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 has zero parameters, so the description does not need to explain parameter meaning. The baseline of 4 applies because there is nothing for the description to compensate for in this dimension.

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?

The description clearly states a specific verb ('Verify') and resource ('current Reddit session validity'), and lists the extracted data (username, karma, notification metrics). It is clear on its own, but it does not explicitly contrast with siblings like reddit_get_profile or reddit_check_inbox, so it stops short of full differentiation.

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?

There is no guidance on when to use this tool versus alternatives such as reddit_get_profile or reddit_check_inbox. The description implies a session-check purpose, but it never states prerequisites, exclusions, or conditions that would route an agent here.

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