List all attachments on a TestRail case. Returns id, filename, size, created_on, user_id per attachment. Read-only — safe without user confirmation. Use this to find attachment ids before calling testrail_get_attachment.
| Name | Required | Description | Default |
|---|---|---|---|
| caseId | Yes | TestRail case id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden for safety disclosure. It explicitly states 'Read-only — safe without user confirmation,' which addresses the safety dimension well. However, it doesn't describe pagination behavior, error cases (e.g., nonexistent caseId), or whether the list is complete or truncated. The read-only disclosure is good but not comprehensive.
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?
Three sentences, every one earning its place: what it does, what it returns, safety note, and usage workflow. Zero waste, well front-loaded with the core purpose first. This is an exemplary concise tool description.
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?
For a simple list tool with one parameter, full schema coverage, and an explicit read-only disclosure, the description covers the essentials. There's no output schema to document return values, but the description does enumerate the returned fields. Minor gaps: no mention of pagination or behavior on invalid caseId, but these are acceptable omissions for a simple look-up tool.
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 100% with a single parameter (caseId) described as 'TestRail case id' with exclusiveMinimum 0. The description doesn't add new parameter information beyond the schema, which the baseline of 3 reflects. With only one well-documented parameter, there's limited scope for description to add value here.
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 states a specific verb+resource (list attachments on a TestRail case) and specifies what fields are returned (id, filename, size, created_on, user_id). It distinguishes itself from the sibling testrail_get_attachment by establishing a clear workflow relationship (find ids before retrieving).
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 provides clear context on when to use it: 'Use this to find attachment ids before calling testrail_get_attachment.' This explicitly names the downstream tool, establishing the intended workflow. It doesn't enumerate when-not-to-use scenarios or alternatives, but the specific workflow linkage is strong 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.
The set contains near-identical duplicate families: web_* and playwright_* expose ~15 pairs of the same desktop-grid-browser operations (web_get_text/playwright_get_text, web_reload/playwright_reload), and screenshot/log/network/mock capabilities each have 5-8 entry points (device_screenshot vs android_mjpeg_screenshot vs ios_screenshot vs ios_fast_screenshot vs web_screenshot vs webpage_screenshot vs session_screenshot). Many individual descriptions carefully draw boundaries (devtools vs traffic, HID vs session), but an agent cannot reliably distinguish web_* from playwright_*, and ios_screenshot/ios_fast_screenshot/ios_mjpeg_screenshot blur together.
The prefix scheme is broken: Android functionality is split arbitrarily between android_* and device_* (device_screenshot vs android_mjpeg_screenshot), the desktop browser gets two parallel prefixes (web_* and playwright_*), and verbs vary across equivalents (device_navigate_url vs web_navigate vs ios_safari_navigate). session_* uses bare verbs (session_url, session_back), and the same concept gets different names (ios_clipboard_get_hid vs ios_get_pasteboard; device_screen vs ios_orientation).
333 tools is an extreme count by any measure — far beyond the 50+ threshold — and much of the bulk is duplicative (the web_*/playwright_* pairs alone double ~15 slots) or out-of-scope for a device-control server (TestRail, Jira, AzDO, agent memory, secret variables, feedback). Even granting that remote device control + test automation is a broad domain, this surface will devastate agent context budgets and is impossible to navigate coherently.
The core device-control and test-automation domain is remarkably thorough: Android and iOS each have full interaction, app-lifecycle, file, network/proxy, performance, crash, accessibility, recording, and replay coverage, with CRUD lifecycles for flows, suites, app uploads, TestRail cases, and visual-review baselines. Minor gaps exist at the margins — Jira/AzDO lack update/transition/comment operations, and iOS cannot open/close tabs — but the central workflows have no dead ends.
