Find Action1 tools by domain: organizations, endpoints, policies, or updates. Use this discovery aid to identify available tools for your needs.
Discover available Action1 tools by domain. All tools are callable at any time — this is a help/discovery aid.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | endpoints (device inventory), organizations (multi-tenant MSP), policies (automation visibility), updates (missing patches). |
Changes observed during successful MCP inspections.
v1.1.2v1.1.0v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it only says this is a 'help/discovery aid' without disclosing read-only nature, output format, side effects, or the fact that it doesn't query any actual data. This is insufficient for the agent to understand the tool's runtime behavior.
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 with no wasted words, and the purpose is front-loaded. It's concise and easy to scan, though it omits some behavioral detail that would increase completeness.
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?
The tool is simple (one parameter, no output schema), but the description doesn't explain what the tool returns or what 'discover' means concretely. Without an output schema, the description should state the expected response (e.g., list of tool names/descriptions) to be considered complete. It leaves a significant gap.
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?
The schema covers 100% of the parameter with descriptions for each enum value, so the baseline is 3. The description adds only the phrase 'by domain', which reinforces the parameter's purpose but doesn't add meaning beyond the schema.
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 uses a specific verb 'Discover' and resource 'available Action1 tools', clearly indicating it's a metadata/help tool rather than a data-returning tool. The phrase 'help/discovery aid' further distinguishes it from sibling list tools, though it doesn't explicitly name them.
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 statement 'All tools are callable at any time — this is a help/discovery aid' gives some context that this tool is for exploration, implying it can be used instead of the specific tools when you need an overview. However, it doesn't explicitly state when to prefer this tool over its siblings or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.