rubrkit_convert_to_rubr_flowStart an async rubr_flow conversion job. Requires rubr_flow:convert for API keys.
| Name | Required | Description | Default |
|---|---|---|---|
| modelTier | No | ||
| outputPath | No | ||
| targetFileId | No | ||
| reasoningEffort | No | ||
| artifactBundleId | Yes | ||
| targetVersionNumber | No | ||
| artifactBundleVersionNumber | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description indicates the tool is async ('start an async ... job') and requires specific permissions. Without annotations, these are useful behavioral traits. However, it omits details like whether it returns a job ID, how to track progress, or side effects.
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?
Two concise sentences with no filler. Essential info (async job, required permission) is front-loaded. Every sentence adds value.
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?
With 7 parameters, no output schema, and no schema descriptions, the description fails to cover key aspects like job lifecycle, return value, polling, or error scenarios. The tool's complexity is not matched by the description.
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?
No parameter descriptions in schema or description. Only artifactBundleId is mentioned as required. Parameter names like modelTier, reasoningEffort, targetFileId, targetVersionNumber, and artifactBundleVersionNumber are not explained, leaving ambiguity. Enums are present but not described.
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?
Description clearly states the tool starts an async conversion job for rubr_flow. The verb 'start' and resource 'rubr_flow conversion' are specific. While it doesn't explicitly distinguish from siblings, the context of sibling tools like read and list conversions provides differentiation.
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?
No guidance on when to use this tool versus alternatives. Only mentions a required permission (rubr_flow:convert). Does not state prerequisites, scenarios, or when to avoid using it.
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.