Skip to main content
Glama

configure_auth

Set up Overleaf account credentials to enable Git-based project management, syncing LaTeX files between local environments and Overleaf.

Instructions

Configure global Overleaf credentials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesOverleaf account email
tokenYesOverleaf git token

Implementation Reference

  • Handler for the 'configure_auth' tool: extracts email and token from arguments and delegates to AuthManager.saveConfig, returning success message.
    case 'configure_auth': {
        const { email, token } = request.params.arguments as any;
        await authManager.saveConfig({ email, token });
        return {
            content: [{ type: 'text', text: 'Successfully configured authentication' }],
        };
    }
  • Input schema definition for the 'configure_auth' tool, specifying required email and token properties.
    inputSchema: {
        type: 'object',
        properties: {
            email: {
                type: 'string',
                description: 'Overleaf account email',
            },
            token: {
                type: 'string',
                description: 'Overleaf git token',
            },
        },
        required: ['email', 'token'],
    },
  • src/index.ts:104-121 (registration)
    Registration of the 'configure_auth' tool in the ListTools response, including name, description, and input schema.
    {
        name: 'configure_auth',
        description: 'Configure global Overleaf credentials',
        inputSchema: {
            type: 'object',
            properties: {
                email: {
                    type: 'string',
                    description: 'Overleaf account email',
                },
                token: {
                    type: 'string',
                    description: 'Overleaf git token',
                },
            },
            required: ['email', 'token'],
        },
    },
  • AuthManager.saveConfig method: merges new config with existing and writes to ~/.overleaf-mcp/config.json.
    async saveConfig(config) {
        const current = await this.getConfig();
        const newConfig = { ...current, ...config };
        await fs.writeJson(CONFIG_FILE, newConfig, { spaces: 2 });
    }
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. 'Configure' implies a write/mutation operation, but the description doesn't state whether this persists credentials across sessions, requires specific permissions, has side effects (e.g., invalidating previous tokens), or what happens on success/failure. For a credential-setting 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, efficient sentence with zero waste. It's front-loaded with the core purpose ('Configure global Overleaf credentials') and avoids unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 a credential-configuration tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects (e.g., persistence, error handling), usage context, or what the tool returns (e.g., success confirmation, error messages). For a mutation tool that likely affects other sibling operations, more context 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%, with both parameters (email and token) clearly documented in the schema. The description adds no additional meaning beyond the schema—it doesn't explain format requirements (e.g., email validation, token generation source) or interdependencies between parameters. Baseline 3 is appropriate when the schema does all 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 'Configure global Overleaf credentials' clearly states the action (configure) and the resource (global Overleaf credentials). It distinguishes this from sibling tools like clone_project or push_changes by focusing on authentication setup rather than project operations. However, it doesn't specify what 'global' means in this context (e.g., system-wide vs. session-wide), which prevents 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., must be called before other tools that require auth), whether it should be used once per session or repeatedly, or what happens if credentials are invalid. With sibling tools like get_status that might also interact with Overleaf, there's no differentiation in usage context.

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/juho127/overleafMCP'

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