Skip to main content
Glama

inoreader_click

Click a numbered element on the current Inoreader page to navigate or interact with it. Use the element number from the last read to act without re-parsing the page.

Instructions

Click a numbered element on the current Inoreader 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>"
    },
    "name": "inoreader_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and largely drops it. It never says whether clicking navigates away, triggers a network request, mutates page state, invalidates the previously issued element numbering, or what happens on an out-of-range element number — all critical for an irreversible UI action.

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 tight sentence with no filler and the action front-loaded. Its brevity is appropriate in form, though it edges toward under-specification rather than genuine economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a stateful, side-effecting UI action with zero annotations and no output schema, so the description is the only place an agent could learn the consequences of clicking and the validity lifetime of element numbers. Neither is covered, leaving a meaningful gap for a tool whose effects are not self-evident.

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% and the single parameter already carries "Element number from the last read" plus a minimum of 1, so the schema does the heavy lifting. The description adds only the notion that numbers come from the current page, not meaningfully more than the schema text.

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?

"Click a numbered element on the current Inoreader page" gives a specific verb (click) and a specific target (a numbered element on the current page), which is enough to distinguish this action tool from siblings like inoreader_open or inoreader_close. It stops short of 5 because it never states what clicking actually accomplishes (navigation, fold/expand, load more, etc.).

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: the element number comes "from the last read," so an agent can infer this must follow inoreader_read, and "current page" implies a required page state. There is no explicit when-to-use versus alternatives, no statement of prerequisites or ordering beyond that inference, and no guidance for what to do instead if no read has occurred.

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