Skip to main content
Glama

patreon_type

Types text into a numbered field on the current Patreon page, using the field number from the last read.

Instructions

Type text into a numbered field on the current Patreon page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "patreon_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and adds little beyond the action itself. It does not say whether typing appends or replaces existing content, whether it clears the field first, whether it submits the form, what happens with an out-of-range element number, or whether the page must be focused.

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, and the key constraint ("current Patreon page") appears early. It is efficient, though extremely terse for a browser-automation action.

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 two-parameter input tool with no output schema, the description covers the core action adequately. It is still thin on the operational context an agent needs for browser automation, notably error behavior and the requirement for a prior page read to know which field number to target.

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%, so both parameters are already documented in the input schema, which sets the baseline at 3. The phrase "numbered field" loosely echoes the element parameter but adds no format, range, or lifecycle detail beyond what the schema states.

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 states a specific verb (type) and resource (text into a numbered field on the current Patreon page), which cleanly distinguishes it from siblings like patreon_click and patreon_read. It stops short of explicitly naming an alternative it is not, but the action is unambiguous.

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 choose this over patreon_click or patreon_read, nor on prerequisites such as first reading the page to obtain a field number. The dependency on a prior read is only hinted at inside the schema's element description, not in the tool description itself.

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