Skip to main content
Glama
folderr-tech

Folderr

Official
by folderr-tech

login

Authenticate users to access Folderr's API for managing and communicating with Assistants using email and password credentials.

Instructions

Login to Folderr with email and password

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesUser email
passwordYesUser password

Implementation Reference

  • The main handler function that executes the 'login' tool logic. It sends a POST request to the Folderr API's sign-in endpoint with email and password, updates the authentication token in config and axios instance upon success, and returns appropriate success or error messages.
    private async handleLogin(args: any) {
      try {
        const response = await this.axiosInstance.post<AuthResponse>('/api/auth/sign-in', {
          email: args.email,
          password: args.password,
        });
    
        // Update config and axios instance with new token
        this.config.token = response.data.token;
        this.axiosInstance.defaults.headers.common['Authorization'] = `Bearer ${this.config.token}`;
        this.saveConfig();
    
        return {
          content: [
            {
              type: 'text',
              text: 'Successfully logged in',
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Login failed: ${error.response?.data?.message || error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema for the 'login' tool, specifying the required 'email' and 'password' fields as strings.
    inputSchema: {
      type: 'object',
      properties: {
        email: {
          type: 'string',
          description: 'User email',
        },
        password: {
          type: 'string',
          description: 'User password',
        },
      },
      required: ['email', 'password'],
    },
  • src/index.ts:125-142 (registration)
    Registration of the 'login' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'login',
      description: 'Login to Folderr with email and password',
      inputSchema: {
        type: 'object',
        properties: {
          email: {
            type: 'string',
            description: 'User email',
          },
          password: {
            type: 'string',
            description: 'User password',
          },
        },
        required: ['email', 'password'],
      },
    },
  • src/index.ts:217-218 (registration)
    Registration of the 'login' tool handler in the CallToolRequestSchema switch statement, dispatching to handleLogin function.
    case 'login':
      return await this.handleLogin(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions authentication but doesn't describe what happens after login (session creation, token generation, expiration), security implications, error conditions, or whether this establishes a persistent session. For a critical authentication tool with zero annotation coverage, this is a significant gap.

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 extremely concise (6 words) and front-loaded with the essential information. Every word earns its place - 'Login to Folderr' establishes the action and target, 'with email and password' specifies the required inputs. No wasted words or unnecessary elaboration.

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?

For an authentication tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (session token, success status, user data), doesn't mention error cases or security requirements, and provides no context about how this integrates with the broader tool ecosystem. Given the critical nature of authentication, more completeness is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters completely. The description adds minimal value beyond what's in the schema by confirming these are the credentials needed for login, but doesn't provide additional context about format requirements, validation rules, or security considerations.

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 ('Login to Folderr') and the required credentials ('with email and password'), making the purpose immediately understandable. However, it doesn't differentiate this authentication tool from sibling tools like 'set_api_token' which might serve a similar authentication purpose through different mechanisms.

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 like 'set_api_token' or whether it's required before using other tools. It simply states what the tool does without context about prerequisites, authentication flow, or relationship to other tools in the server.

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/folderr-tech/folderr-mcp-server'

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