Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_authenticated_user

Retrieve authenticated user details from Qiita, a Japanese developer community platform, for API interactions and user-specific operations.

Instructions

認証されたユーザーの詳細情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_authenticated_user' tool. It has an empty input schema and executes by calling the QiitaApiClient's getAuthenticatedUser method.
    get_authenticated_user: {
      schema: z.object({}),
      execute: async (_, client) => client.getAuthenticatedUser(),
    },
  • The MCP tool definition (for listing tools) with name, Japanese description, and empty input schema.
    {
      name: 'get_authenticated_user',
      description: '認証されたユーザーの詳細情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Core helper function in QiitaApiClient that performs the actual API call to retrieve the authenticated user after checking authentication.
    async getAuthenticatedUser() {
      this.assertAuthenticated();
      const response = await this.client.get('/authenticated_user');
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it indicates this retrieves user details, it doesn't disclose what authentication is required, whether this is a read-only operation, what specific details are returned, or any rate limits/constraints. For a user information tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient Japanese sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

Given this is a simple retrieval tool with 0 parameters and no output schema, the description provides the basic purpose but lacks important context. Without annotations or output schema, it should ideally mention what authentication is required and what kind of user details are returned. The description is minimally adequate but has clear gaps.

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 has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description correctly doesn't mention any parameters, which is appropriate. Baseline for 0 parameters is 4, and the description doesn't add or detract from parameter understanding.

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 clearly states the action ('取得します' - get/retrieve) and the resource ('認証されたユーザーの詳細情報' - authenticated user's detailed information). It distinguishes from siblings like 'get_user' which presumably gets any user, while this specifically gets the authenticated user. However, it doesn't explicitly contrast with 'get_user' which would make it a 5.

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?

The description implies this should be used when you need information about the currently authenticated user, but doesn't explicitly state when to use this vs. 'get_user' (which likely requires a user ID parameter). There's no guidance about prerequisites (authentication required) or alternatives, leaving usage context somewhat implied rather than explicit.

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/Selenium39/mcp-server-qiita'

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