Skip to main content
Glama
dl4rce

flaiwheel

by dl4rce
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

git_pull_reindex

Pull git commits and re-index only changed files to synchronize the knowledge base with .md file updates.

Instructions

Pull latest commits from the knowledge repo git remote, then re-index.

    Call this AFTER pushing .md files to the knowledge repo. Runs
    'git pull' on the cloned docs directory, then re-indexes only changed
    files. No-op if the repo is already up to date.

    Requires MCP_GIT_REPO_URL to be configured. Use reindex() instead
    when files were written locally (not via git push).

    Args:
        project: Target project name (optional)

    Returns:
        "Already up to date" if no changes, otherwise files indexed,
        chunks upserted, and stale chunks removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Describes the workflow (git pull then re-index only changed files), notes it's a no-op if up-to-date, and indicates what returns. Lacks explicit mention of network usage or potential side effects, but covers main behavior.

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?

Description is concise, uses bullet points for clarity, and front-loads the main purpose. Every sentence adds value.

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

Completeness4/5

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

Given the presence of an output schema, the description covers prerequisites, behavior variations, and return states. Could elaborate on project parameter usage, but overall sufficient.

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

Parameters2/5

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

The single parameter 'project' is only described as 'Target project name (optional)', which adds no meaning beyond the schema's type and default. With 0% schema coverage, the description should provide more context, e.g., how project filtering works or what default project is used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (pull and re-index), the trigger (after pushing .md files), and distinguishes from the sibling tool 'reindex' by specifying when to use each.

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

Usage Guidelines5/5

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

Explicitly states when to call (after pushing .md files), when not to (use reindex for local writes), and mentions the prerequisite MCP_GIT_REPO_URL configuration.

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/dl4rce/flaiwheel'

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