Skip to main content
Glama
caseSHY

caseSHY/aicoreutils

by caseSHY
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

ginstall

Destructive

Copy files with permission and ownership settings, or create directories. Destructive operation; use --dry_run to preview changes. Returns JSON paths and status.

Instructions

Copy files and set attributes like permissions and ownership — GNU-compatible alias for 'install'. Destructive: creates or overwrites target files, creates directories with --directory/--parents, and changes file metadata. Default mode is 755. Use --dry_run to preview without touching the filesystem. Returns JSON with installation paths and status. Use when GNU install semantics or BSD-compatible behavior is needed. Not for simple copying — use 'cp' for copying without permission setting. Not for the standard install interface — use 'install'. See also 'install', 'cp'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allow_overwriteNoAllow replacing an existing destination.
directoryNoCreate directories instead of installing a file.
dry_runNoReport operations without changing files.
modeNoOctal mode applied to installed paths.755
parentsNoCreate missing parent directories.
pathsNoSOURCE DESTINATION, or directories with --directory.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Description adds context beyond annotations: destructive behavior (overwrites, creates directories), default mode 755, dry-run option. No contradiction with destructiveHint annotation.

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?

Single paragraph with front-loaded purpose, then behavioral details, then usage guidelines. Every sentence is informative and concise.

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?

Covers return value (JSON with paths and status), destructive nature, dry-run, and alternatives. Complete for a tool with optional parameters and no output schema.

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 covers all 6 parameters with descriptions (100% coverage), so description adds minimal extra meaning beyond summarizing defaults and usage.

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?

Description clearly states 'Copy files and set attributes' with GNU-compatible alias for install, distinguishing from siblings like cp and install.

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 use (GNU install semantics) and when not to (simple copying, use cp; standard install, use install), with alternative tool names.

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/caseSHY/AI-CLI'

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