Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_search_resources

Search Autotask for resources by name or email. Filter by active status, resource type, and paginate through results up to 500 per page.

Instructions

Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTermNoSearch term for resource name or email
isActiveNo
resourceTypeNoFilter by resource type (1=Employee, 2=Contractor, 3=Temporary)
pageNo
pageSizeNoMax 500
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Only discloses default page size and pagination; omits other behaviors like search scope or read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two succinct sentences efficiently communicate purpose and a key detail, with no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fails to describe the return format or fields, which is important for a search tool without an output schema. The description is too brief for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60% with three parameters described. Description adds marginal value by clarifying pagination defaults but does not compensate for undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for resources (users) in Autotask, distinguishing it from other entity-specific search tools by explicitly naming the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides basic pagination guidance but lacks direction on when to use this tool versus alternative search tools for contacts or companies, and does not mention filtering options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asachs01/autotask-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server