Skip to main content
Glama
folderr-tech

Folderr

Official
by folderr-tech

set_api_token

Configure API authentication for the Folderr MCP server by providing a token to enable interaction with Folderr Assistants without using login credentials.

Instructions

Set an API token for authentication (alternative to login)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesAPI token generated from Folderr developers section

Implementation Reference

  • The handler function that executes the set_api_token tool logic: updates the configuration with the provided token, sets the Authorization header on the axios instance, saves the config to file, and returns a success or error response.
    private async handleSetApiToken(args: any) {
      try {
        // Update config and axios instance with new token
        this.config.token = args.token;
        this.axiosInstance.defaults.headers.common['Authorization'] = `Bearer ${this.config.token}`;
        this.saveConfig();
    
        return {
          content: [
            {
              type: 'text',
              text: 'Successfully set API token',
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to set API token: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for the set_api_token tool, defining a required 'token' property of type string.
    inputSchema: {
      type: 'object',
      properties: {
        token: {
          type: 'string',
          description: 'API token generated from Folderr developers section',
        },
      },
      required: ['token'],
    },
  • src/index.ts:111-124 (registration)
    Registration of the set_api_token tool in the ListToolsRequestSchema handler, providing name, description, and input schema.
    {
      name: 'set_api_token',
      description: 'Set an API token for authentication (alternative to login)',
      inputSchema: {
        type: 'object',
        properties: {
          token: {
            type: 'string',
            description: 'API token generated from Folderr developers section',
          },
        },
        required: ['token'],
      },
    },
  • src/index.ts:219-220 (registration)
    Switch case in the CallToolRequestSchema handler that dispatches calls to the set_api_token tool to the handleSetApiToken method.
    case 'set_api_token':
      return await this.handleSetApiToken(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 the full burden of behavioral disclosure. While it indicates this is for authentication, it doesn't describe what happens when the token is set (e.g., persistence across sessions, scope of authentication, error behavior if token is invalid, or whether it overwrites existing tokens). For a security-critical 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 perfectly concise with a single sentence that contains zero wasted words. It's front-loaded with the core purpose and includes the essential contextual information about being an alternative to login, making every word earn its place.

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 the tool's moderate complexity (authentication operation with one parameter) and 100% schema coverage but no annotations or output schema, the description provides adequate basic context about purpose and alternative usage. However, it lacks important behavioral details about how the authentication works and what happens after token setting, leaving gaps for a security-related tool.

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?

The input schema has 100% description coverage, with the 'token' parameter well-documented as 'API token generated from Folderr developers section'. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Set') and resource ('API token for authentication'), making it immediately understandable. It distinguishes from the sibling 'login' tool by mentioning it's an alternative, though it doesn't fully differentiate from other potential authentication methods beyond this sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by explicitly stating this is an 'alternative to login', which helps the agent understand when to use this tool versus the sibling 'login' tool. However, it doesn't specify when to prefer one over the other or mention any prerequisites or exclusions for using this authentication method.

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