Skip to main content
Glama
ypollak2

ypollak2/llm-router

by ypollak2
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

llm_fs_rename

Generates shell commands to rename or reorganize files from a natural language description. Dry-run mode shows echo-prefixed commands for safe review.

Instructions

Generate shell commands for a file rename/reorganisation operation.

Describe what you want to rename and the cheap model produces the mv/git mv
commands. Use ``dry_run=True`` (default) to get echo-prefixed commands safe
to inspect before running.

Args:
    description: What to rename and how, e.g. "rename all _old.py files in
        src/ to remove the _old suffix" or "move all test_*.py files from
        tests/unit/ into tests/".
    dry_run: When True, commands are prefixed with ``echo`` for safe review.
        Set to False to get directly executable commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

With no annotations, the description covers key behavior: outputs shell commands, default dry_run prefix for safety, and ability to get executable commands. It does not disclose exact return format but output schema exists.

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 efficient: a brief opening sentence, clear usage note, and concise Args section. No redundant information, every sentence adds value.

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?

Given simple inputs and existence of output schema, the description adequately covers input semantics and safety mode. No need to detail return values per rules.

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

Parameters5/5

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

Both parameters are explained beyond schema: description has concrete examples (e.g., 'rename all _old.py files') and dry_run clarifies echo prefix behavior. This fully compensates for 0% schema description coverage.

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 'Generate shell commands for a file rename/reorganisation operation', specifying the verb and resource. It distinguishes from siblings like llm_fs_find and llm_fs_edit_many by focusing on rename operations.

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 explains using dry_run=True for safe inspection and provides examples of when to describe desired renames. It does not explicitly exclude alternative tools but implies use for file rename tasks.

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/ypollak2/llm-router'

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