Access and manage group details in Freshdesk by querying specific group IDs, enabling streamlined support ticket organization and customer service automation.
View a group in Freshdesk.
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It only repeats the name and does not disclose return format, error behavior, or whether the operation is read-only (though the verb 'view' implies it).
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 sentence with zero wasted words, making it highly concise. It lacks structure but is appropriately brief for a simple lookup tool.
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 tool with no output schema and no annotations, the description provides minimal information. It does not explain what fields are returned, how to handle a missing group, or any necessary permissions or 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 defines only a required integer group_id, but with 0% schema description coverage, neither the schema nor the description explains what group_id refers to or how to obtain it. The description adds no semantic value for the parameter.
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 clear action ('view') and resource ('a group'), making it obvious that this tool retrieves a single group. It is distinguishable from sibling tools like list_groups by the singular scope, though it does not explicitly name alternatives.
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 is provided on when to use this tool instead of list_groups or other group-related tools. The description only states what it does, giving no context on the appropriate scenario for using this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.