Skip to main content
Glama
OrgMentem

zotio

by OrgMentem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

command_run

Destructive

Run one mirrorable Cobra command by its space-separated command path.

Instructions

Run one mirrorable Cobra command by its space-separated command path.

Input Schema

NameRequiredDescriptionDefault
argsNoAdditional positional arguments only; raw flags rejected.
nameYesExact space-separated command path to run, such as "items enrich".
flagsNoSafe flags to pass by name: command-local flags plus, for mutating commands, the write-safety gate flags (yes, dry-run, allow-destructive, allow-zotero-cloud, max-changes, continue-on-error, max-failures); read-only commands that write local files expose dry-run only. "yes": Apply writes (otherwise preview only) — pass {"yes": true} to apply a write. Inspect available flags via command_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.30.0
    • changedInput schema / properties / flags / description
      Previous value: -"Safe flags to pass by name: command-local flags plus, for mutating commands, the write-safety gate flags (yes, dry-run, allow-destructive, allow-zotero-cloud, max-changes, continue-on-error, max-failures) — pass {\"yes\": true} to apply a write. Inspect available flags via command_search."New value: +"Safe flags to pass by name: command-local flags plus, for mutating commands, the write-safety gate flags (yes, dry-run, allow-destructive, allow-zotero-cloud, max-changes, continue-on-error, max-failures); read-only commands that write local files expose dry-run only. \"yes\": Apply writes (otherwise preview only) — pass {\"yes\": true} to apply a write. Inspect available flags via command_search."
  2. Changed1 schema field changedv0.19.0
    • changedInput schema / properties / flags / description
      Previous value: -"Safe flags to pass by name: command-local flags plus, for mutating commands, the write-safety gate flags (yes, dry-run, allow-destructive, max-changes, continue-on-error, max-failures) — pass {\"yes\": true} to apply a write. Inspect available flags via command_search."New value: +"Safe flags to pass by name: command-local flags plus, for mutating commands, the write-safety gate flags (yes, dry-run, allow-destructive, allow-zotero-cloud, max-changes, continue-on-error, max-failures) — pass {\"yes\": true} to apply a write. Inspect available flags via command_search."
  3. First observedv0.7.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructive=true, openWorld=true, and readOnly=false, so the safety profile is visible outside the description. The description itself adds almost no behavioral context beyond the annotations, but it does not contradict them.

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 front-loaded sentence with no filler. It is concise and structurally clean, even if the content is thin.

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 destructive, open-world command runner with arbitrary Cobra commands and no output schema, the description leaves important context unexplained: what 'mirrorable' means, how commands are discovered, preview versus apply behavior, and what execution returns. The rich schema and annotations help, but the description itself is too thin.

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 description coverage is 100%, so the schema already documents name, args, and flags. The description's mention of 'space-separated command path' largely repeats the name parameter schema and adds no extra parameter semantics.

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 states a specific verb ('Run') and resource ('one mirrorable Cobra command') qualified by the command path. It is reasonably clear what the tool does, though 'mirrorable' is undefined and it does not explicitly contrast with command_search.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. It implies execution of a command path, but does not tell the agent when to use command_run versus command_search or other siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools