Skip to main content
Glama

push_changes

Commit and push LaTeX project changes from local machine to Overleaf using Git integration.

Instructions

Commit and push changes to Overleaf

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localPathYesThe local path of the project
messageYesCommit message

Implementation Reference

  • Executes the core logic of the push_changes tool: checks if local directory exists, stages all changes, checks for any changes via git status, commits with the message if changes present, pushes to Overleaf remote, handles errors.
    async pushChanges(localPath: string, message: string) {
        if (!await fs.pathExists(localPath)) {
            throw new Error(`Directory ${localPath} does not exist`);
        }
    
        const git: SimpleGit = simpleGit(localPath);
        try {
            await git.add('.');
            const status = await git.status();
            if (status.staged.length === 0 && status.created.length === 0 && status.modified.length === 0 && status.deleted.length === 0 && status.renamed.length === 0) {
                return { success: true, message: 'No changes to commit' };
            }
    
            await git.commit(message);
            await git.push();
            return { success: true, message: 'Pushed changes to Overleaf' };
        } catch (error: any) {
            throw new Error(`Failed to push changes: ${error.message}`);
        }
    }
  • src/index.ts:72-89 (registration)
    Registers the push_changes tool in the ListToolsRequestHandler response, defining its name, description, and input schema (localPath: string, message: string).
    {
        name: 'push_changes',
        description: 'Commit and push changes to Overleaf',
        inputSchema: {
            type: 'object',
            properties: {
                localPath: {
                    type: 'string',
                    description: 'The local path of the project',
                },
                message: {
                    type: 'string',
                    description: 'Commit message',
                },
            },
            required: ['localPath', 'message'],
        },
    },
  • MCP CallToolRequest handler case for push_changes: parses arguments, delegates to GitManager.pushChanges, serializes and returns the result as text content.
    case 'push_changes': {
        const { localPath, message } = request.params.arguments as any;
        const result = await gitManager.pushChanges(localPath, message);
        return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
    }
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 'Commit and push changes' implies a write/mutation operation, it doesn't specify critical details like required permissions, whether it's destructive to remote data, error conditions, or typical response format. This leaves significant gaps for a tool that modifies remote state.

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 wasted words. It's appropriately sized for a tool with two parameters and no complex behavioral nuances to explain, making it easy to parse.

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 a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'changes' entail (e.g., staged files?), what happens on success/failure, or how it interacts with sibling tools. Given the complexity of a git-like operation, more context is needed for reliable use.

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, clearly documenting both parameters ('localPath' and 'message'). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score when schema coverage is high.

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 ('Commit and push changes') and the target resource ('to Overleaf'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'pull_changes' or 'get_status', 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 like 'pull_changes' or 'configure_auth'. It doesn't mention prerequisites (e.g., needing authentication or existing changes) or exclusions, leaving the agent to infer 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