Fetch details for a specific collector group by its ID, including configuration and status, to aid in monitoring infrastructure.
Get details about a specific collector group
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | Collector group ID |
Changes observed during successful MCP inspections.
v4.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description does not need to restate that. It adds only the 'specific' scoping and no additional behavioral context such as error behavior or response contents.
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 a single front-loaded sentence with no filler. It communicates the operation and scope immediately.
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 one-parameter read-only getter with strong annotations and no nested objects, this description is sufficient for basic invocation. It does not enumerate returned fields, but 'details' plus the schema and annotations provide enough context.
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 fully documents group_id with 100% coverage, so the baseline of 3 applies. The description does not add any meaning beyond the schema's 'Collector group ID'.
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 the verb 'Get' with the resource 'collector group' and 'specific' signals a single-entity lookup by ID. This clearly distinguishes it from get_collector_groups (list all) and get_collector (a collector, not a group).
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 explicit guidance is given about when to use this tool versus alternatives such as get_collector_groups or get_collector. The intended usage is only implied by the singular phrasing and the parameter name, not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.