autotask_get_quote
Retrieve a specific quote by its ID from Autotask PSA to view details and status.
Instructions
Get a specific quote by ID
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| quoteId | Yes | The quote ID to retrieve |
Retrieve a specific quote by its ID from Autotask PSA to view details and status.
Get a specific quote by ID
| Name | Required | Description | Default |
|---|---|---|---|
| quoteId | Yes | The quote ID to retrieve |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations or behavioral details beyond a simple read operation. Does not disclose error handling, authentication needs, or what happens if quote does not exist.
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?
Single, clear sentence with no unnecessary words. Front-loaded with verb and resource.
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 read operation with no output schema, the description does not explain what is returned (e.g., quote details). Incomplete for an agent to fully understand the tool's output.
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 parameter description 'The quote ID to retrieve'. The tool description adds no additional 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?
Description clearly states 'Get a specific quote by ID', specifying the verb (get) and resource (quote) and identifier (by ID). Distinguishes from sibling tools like autotask_create_quote and autotask_search_quotes.
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 versus alternatives like autotask_search_quotes. No context about prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/autotask-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server