rubrkit_read_drift_observationsList the recorded observations for a drift monitor via /api/v1/drift-monitors/{driftMonitorId}/observations. Requires artifact_bundles:read (or artifacts:pull) for API keys.
| Name | Required | Description | Default |
|---|---|---|---|
| driftMonitorId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It gives permission requirements and the API endpoint, but does not disclose response format, pagination, or ordering. For a read-only list tool, it is moderately transparent but could be improved.
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 sentences, front-loaded with the action. The API path could be implied, but it is not overly verbose. Efficient for the information provided.
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?
Given the simple parameter set and lack of output schema, the description covers the basic purpose and permissions. However, it lacks details on return format, pagination, error codes, or example usage, leaving some context incomplete.
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 coverage is 0%, so the description must compensate. However, it does not explain the parameter 'driftMonitorId' beyond what the schema provides (type, format). No additional meaning or context.
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 action (List), the resource (observations for a drift monitor), and the API endpoint. It distinguishes this tool from sibling tools like 'rubrkit_list_drift_monitors' which lists monitors, not observations.
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 vs alternatives, no prerequisites or exclusions. Only mentions permission requirements, which is minimal guidance.
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.