rubrkit_restore_artifact_bundle_versionRestore files from a prior artifact-bundle version by creating new file versions. Requires artifact_bundles:write and files:write for API keys.
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| versionNumber | Yes | ||
| artifactBundleId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool creates new file versions to restore, which is the core behavior. However, it omits details such as whether the operation is destructive, idempotent, or has side effects. Adequately minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states the purpose, the second provides required permissions. No unnecessary words, front-loaded, and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, and the description does not mention return values, error conditions, or prerequisites beyond permissions. For a restoration tool, this leaves significant gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning the description adds no meaning to the parameters. The agent must infer from parameter names and types (e.g., artifactBundleId, versionNumber, message) without any textual explanation. The description does not clarify the role of 'message' or other details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Restore files from a prior artifact-bundle version' and identifies the resource as an artifact-bundle version. However, it does not explicitly differentiate from the sibling tool 'rubrkit_restore_file_version', which restores a single file version.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes required permissions but provides no guidance on when to use this tool versus alternatives like 'rubrkit_restore_file_version'. No when-to-use or when-not-to-use context is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resource-action pairs, and descriptions clarify differences like soft vs hard delete or list bundles vs list versions. However, some names are similar (e.g., delete_artifact_bundle vs hard_delete_artifact_bundle), which could cause minor confusion.
All tools follow a uniform rubrkit_verb_noun pattern with imperative verbs and snake_case, making them predictable and easy to navigate. No mixed conventions or inconsistencies.
With 30 tools, the server is comprehensive but slightly heavy for a single-purpose MCP. The tools cover multiple sub-domains (bundles, files, audits, evals, conversions, docs), which justifies the count, but consolidation could reduce complexity.
The set covers CRUD for artifact bundles, file operations, audit/eval lifecycle, and API documentation. Minor gaps include missing bundle metadata update and file deletion, but core workflows are supported.