Skip to main content
Glama

inoreader_guide

Get guidance on Inoreader screens, sign-in, reading articles, organizing feeds, and drafting rules; call this first when you need to know how to perform an Inoreader task.

Instructions

How to work in Inoreader (read articles, organize feeds and create rules): 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": "inoreader_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Inoreader, 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 provided, so the description carries the full disclosure burden. It states the guide contains screens and a sign-in link, which hints it returns reference material rather than performing actions, but it does not clarify whether it requires authentication, whether it navigates or has side effects, or what the output looks like. Useful context, but incomplete for a no-annotation tool.

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?

It is a single compact sentence with a clarifying parenthetical and no filler. The most actionable instruction ('Call this first') sits at the end rather than being front-loaded, which is a minor structural miss.

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 one-param, no-annotation, no-output-schema tool, the description gives the essentials: what it is and when to call it. It does not describe the return content or interaction model, so a modest gap remains given the absence of structured behavioral cues.

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?

The single optional 'task' parameter has 100% schema description coverage, so the schema already explains it. The description adds no extra meaning about how the free-form task string is interpreted, so 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?

The description names a specific resource and scope: a guide to working in Inoreader covering articles, feed organization, rules, screens, and the sign-in link. This distinguishes it from the action-oriented siblings (click, open, read, type) as an orientation/reference tool. It stops short of a crisp one-line 'this is the how-to' statement, but the intent is clear.

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 an explicit ordering directive that tells the agent to invoke it before the other Inoreader tools. There are no explicit when-not-to-use conditions or named alternatives, but the sequencing guidance is concrete and actionable.

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