Skip to main content
Glama

patreon_guide

Get step-by-step guidance on Patreon creator posts, members, tiers, screens, and the sign-in link before starting a Patreon task.

Instructions

How to work in Patreon (creator posts, members and tiers): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Patreon, in your words.

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 full behavioral burden. It implies a read-only informational tool and says it covers screens and the sign-in link, but it does not state the form of the response (text instructions vs. structured data), whether it has any side effects, or whether it needs auth for the sign-in link.

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?

Two short clauses with no filler, and the covered domains are stated before the imperative. The critical 'Call this first' cue is placed last rather than front-loaded, which is a minor structural weakness.

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?

For a simple one-optional-param orientation tool with no output schema, the definition covers what topic areas the guide addresses, which is the main thing an agent needs. It is still thin on what the caller actually receives back and how the 'task' input shapes that output.

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

Parameters3/5

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

Schema description coverage is 100% for the single optional 'task' parameter, so the schema already explains it. The description never mentions the task parameter or how phrasing it changes the guidance returned, so it adds nothing beyond the schema; baseline 3 applies.

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 resource (a Patreon how-to guide) and scopes it with 'creator posts, members and tiers', plus 'its screens and the sign-in link'. It is clearly distinguishable from the action siblings (patreon_click, patreon_open, patreon_read), though the phrase 'How to work in Patreon' is a bit broad on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' is explicit sequencing guidance that tells the agent when to reach for this tool relative to the other patreon_* tools. There is no when-not condition or statement of what to do after calling it, but the primary routing cue is present and unambiguous.

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