Skip to main content
Glama
dl4rce

flaiwheel

by dl4rce
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

check_update

Check if a newer version of your Flaiwheel server is available on GitHub. Compares version tags to the running version and provides an upgrade command if needed.

Instructions

Check whether a newer Flaiwheel version is available on GitHub. Read-only.

    Makes a single network request to GitHub (git ls-remote) to compare
    version tags against the running version. No files are modified.
    Use when you suspect Flaiwheel may be outdated, or periodically to
    keep the server current.

    Returns:
        "Up to date" message, or the available version number plus the
        exact bash command to give the user for upgrading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

The description fully discloses behavior: read-only, single network request, no file modifications. Since annotations are absent, the description carries the burden effectively.

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 concise and well-structured: a summary line, a list of behavioral details, and return value description. No unnecessary words.

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

Completeness5/5

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

The tool is simple with no parameters and an output schema. The description explains the return values and the single action, making it complete for this context.

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

Parameters4/5

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

The input schema has zero parameters, so schema coverage is 100%. The description adds no parameter info, but with no parameters, the baseline is 4.

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 tool checks for a newer Flaiwheel version on GitHub, with a specific verb and resource. It distinguishes from siblings by focusing on version checking, which no other tool does.

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 explicit usage context: 'Use when you suspect Flaiwheel may be outdated, or periodically to keep the server current.' No exclusion of alternatives is given, but no sibling tool performs this function, so it remains clear.

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