Skip to main content
Glama

patreon_status

Checks that your Cotlet.dev account, credits, and Patreon connection are ready, helping you confirm setup before managing Patreon content.

Instructions

Check that your Cotlet.dev account and Patreon are ready: account, credits and Patreon connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 burden of behavioral disclosure. It discloses the scope of the check (account, credits, Patreon connection) but not whether it is read-only, whether it performs network/auth calls, or what happens on failure — though for a zero-parameter status probe the implied risk is low.

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 enumerated checks read cleanly after the colon. The 'Cotlet.dev' branding is slightly ambiguous but does not bloat the text.

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 partially compensates by naming the three results an agent should expect (account, credits, Patreon connection). For a zero-parameter readiness check this is nearly sufficient, though it does not say what a failing or partial status looks like.

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 no parameters, so there is nothing for the description to clarify beyond the schema; a baseline of 4 applies. The description correctly focuses on what is inspected rather than on 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?

The description gives a concrete verb ('Check') and enumerates the three things verified: account, credits, and Patreon connection. It is clear what the tool does, but it does not distinguish itself from the sibling tools (patreon_open, patreon_read, patreon_guide, etc.), leaving the agent to infer that this is a pre-flight readiness probe rather than an action.

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?

The phrasing 'ready' implies a pre-flight check before using other Patreon tools, but the description never states when to call it, when not to, or which sibling it substitutes for. Usage is only implied, not prescribed.

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