Skip to main content
Glama

Get user info

get_user_info
Read-onlyIdempotent

Retrieve the authenticated Inoreader user's profile details. Use it to confirm identity or account context before managing feeds and subscriptions.

Instructions

Get current authenticated user information. Costs 1 Zone 1 request. Base costs exclude safe-read retries (up to 4 attempts, each counted); honor cached status/cooldown. Never blindly replay uncertain writes. See inoreader://usage for limits, URI examples and prompts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely non-obvious behavior: it costs 1 Zone 1 request, base costs exclude up to 4 counted safe-read retry attempts, and cached status/cooldown must be honored. The trailing 'never blindly replay uncertain writes' line is boilerplate that adds nothing for a read-only, idempotent tool but does not contradict the annotations.

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

Conciseness3/5

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

The purpose is front-loaded, which is good, but the retry/cooldown and write-replay sentences are quota boilerplate aimed at mutating calls and are off-target for a zero-argument read. Roughly a third of the text does not earn its place for this specific tool.

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 trivial zero-parameter call the description is adequate: it names the operation and documents cost/quota behavior. However, with no output schema, nothing tells the agent what 'user information' actually contains (id, username, profile fields), which is the remaining meaningful gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema coverage figure of 100% on an empty property set reinforces that no parameter explanation is needed.

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 opens with a specific verb and resource: 'Get current authenticated user information.' That is unambiguous and no sibling tool in the list covers user identity (they cover feeds, articles, tags, auth setup), so disambiguation is implicit rather than stated. It stops short of a 5 because it never names a sibling or scope boundary.

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 call this versus alternatives (e.g. setup_auth for credentials, get_rate_limit_status for quota). The only conditional text concerns cost accounting and cooldowns, not tool selection. An agent must infer that this is the identity lookup.

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