Skip to main content
Glama

Current User

affine_current_user

Retrieve details of the currently signed-in user within the AFFiNE MCP Server, facilitating user authentication and session management for workspace operations.

Instructions

Get current signed-in user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the affine_current_user tool. It executes a GraphQL query to fetch the current user's details (id, name, email, etc.) and returns them as text.
    const currentUserHandler = async () => {
      const query = `query Me { currentUser { id name email emailVerified avatarUrl disabled } }`;
      const data = await gql.request<{ currentUser: any }>(query);
      return text(data.currentUser);
    };
  • The input/output schema for the tool, with empty inputSchema indicating no parameters required, title and description provided.
    {
      title: "Current User",
      description: "Get current signed-in user.",
      inputSchema: {}
  • The registration of the "affine_current_user" tool using server.registerTool, linking the schema and handler.
    server.registerTool(
      "affine_current_user",
      {
        title: "Current User",
        description: "Get current signed-in user.",
        inputSchema: {}
      },
      currentUserHandler as any
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves the current user but omits critical details: whether it requires authentication, what data it returns (e.g., user ID, email, permissions), or if it has side effects like logging. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence that directly states the tool's function without any fluff. It is front-loaded and efficiently communicates the core purpose, making it easy for an AI agent to parse and understand quickly. Every word earns its place.

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

Completeness2/5

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

Given the complexity of user retrieval (which often involves authentication and data formatting) and the absence of both annotations and an output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., user object structure) or any behavioral nuances, leaving the agent with incomplete context for effective use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately avoids discussing parameters, focusing solely on the tool's purpose. This aligns with the baseline expectation for tools without parameters, earning a high score for not adding unnecessary information.

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') and resource ('current signed-in user'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'affine_update_profile' or 'affine_change_password' by focusing on retrieval rather than modification. However, it doesn't explicitly contrast with other user-related tools, keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication status), nor does it suggest scenarios where this tool is preferred over others like 'affine_update_profile' for user data. This lack of contextual direction leaves usage ambiguous.

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

Related 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/DAWNCR0W/affine-mcp-server'

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