Skip to main content
Glama

Set up Inoreader authentication

setup_auth
Destructive

Generate an Inoreader OAuth 2.0 authorization URL or exchange a callback code once for access tokens to connect the MCP server.

Instructions

Authenticate with Inoreader via OAuth 2.0. If no code is provided, returns the authorization URL to visit. If a code is provided, exchanges it once for access tokens (overwrites locally saved credentials; OAuth requests are separate from Zone 1/2 accounting). A consumed code must not be replayed. Read inoreader://usage for workflow and budget guidance.

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

Input Schema

NameRequiredDescriptionDefault
codeNoAuthorization code from the OAuth callback URL (the 'code' query parameter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by naming what is actually destroyed ('overwrites locally saved credentials'), which concretizes destructiveHint=true, and by stating the code is exchanged once and must not be replayed, which concretizes idempotentHint=false. It further discloses that OAuth requests are excluded from Zone 1/2 accounting, a behavioral fact no annotation or schema conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action and then the two conditional branches. Every clause carries operational information — no restatement of the name or title, no filler.

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

Completeness5/5

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

For a one-parameter auth tool with no output schema, the description covers everything an agent needs: what each call mode returns, the credential-overwrite side effect, the no-replay constraint, and where to find the full workflow. The absence of an output schema is offset by the description naming the two return shapes.

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?

Schema coverage is 100% and the single parameter is already documented as the 'code' query parameter from the callback URL, so the baseline is 3. The description earns an extra point by explaining the semantics the schema does not: the code is single-use, exchanged once, and a consumed code must not be replayed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Authenticate with Inoreader via OAuth 2.0') and immediately decomposes it into its two concrete modes: returning an authorization URL vs. exchanging a code for tokens. No sibling tool in the list does authentication, so the scope is unambiguous from the first sentence alone.

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

Usage Guidelines5/5

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

Gives explicit branching conditions: call without 'code' to get the authorization URL, call with 'code' to exchange it. It also points the agent at 'inoreader://usage' for workflow and budget guidance, which is the right routing for a multi-step OAuth flow that cannot be inferred from the schema.

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