Skip to main content
Glama

get_user_info

Retrieve current user details from FreshRSS instances to access account information and manage RSS feed subscriptions.

Instructions

Get current user information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function that executes the tool logic for 'get_user_info'.
    wrapTool('get_user_info', async () => {
      const info = await client.stats.getUserInfo();
    
      const lines = [
        `**User ID:** ${info.userId}`,
        `**Username:** ${info.userName}`,
        info.userEmail !== undefined && info.userEmail !== '' ? `**Email:** ${info.userEmail}` : '',
      ].filter((line) => line !== '');
    
      return textResult(lines.join('\n'));
    })
  • Registration of the 'get_user_info' tool within the MCP server.
    server.registerTool(
      'get_user_info',
      {
        description: 'Get current user information',
        inputSchema: z.object({}).strict(),
      },
      wrapTool('get_user_info', async () => {
        const info = await client.stats.getUserInfo();
    
        const lines = [
          `**User ID:** ${info.userId}`,
          `**Username:** ${info.userName}`,
          info.userEmail !== undefined && info.userEmail !== '' ? `**Email:** ${info.userEmail}` : '',
        ].filter((line) => line !== '');
    
        return textResult(lines.join('\n'));
      })
    );
  • The underlying service method that makes the API request for 'getUserInfo'.
    async getUserInfo(): Promise<UserInfo> {
      return this.http.get<UserInfo>('/reader/api/0/user-info');
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a cached operation, what format the user information takes, privacy sensitivity of returned data, or whether it requires specific permissions. The phrase 'Get' implies read-only, but this isn't explicit.

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?

The description is appropriately terse for a zero-parameter tool. It front-loads the action and subject without filler words, making it scannable. Given the simplicity of the operation, the brevity is justified.

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?

While the tool concept is simple, the lack of an output schema means the description should ideally hint at the return structure (e.g., 'returns user profile including username and email'). As written, it meets minimum viability but leaves the agent uncertain about what data fields to expect in the response.

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 input schema has zero parameters, which per guidelines establishes a baseline of 4. The description doesn't need to compensate for missing parameter documentation, though it doesn't add any context about why no parameters are needed (e.g., 'uses current authenticated session').

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

Purpose3/5

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

The description states the basic action ('Get') and resource ('current user information'), but 'information' is vague—it doesn't specify whether this returns profile data, preferences, account settings, or authentication status. While it implicitly distinguishes from feed/folder management siblings, the lack of specificity on what user data is returned limits its utility.

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?

No guidance provided on when to use this versus other tools, prerequisites (e.g., authentication requirements), or when not to use it. The description stands alone without contextual usage hints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alysson-souza/freshrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server