Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_get_company_site_configuration

Retrieve company site configuration records by providing a company ID. Use this to discover available fields for further queries.

Instructions

Get company site configuration records. Call first to discover available fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesThe company ID whose site configuration records should be returned

Implementation Reference

  • Schema definition for autotask_get_company_site_configuration tool, requiring a companyId parameter.
    name: 'autotask_get_company_site_configuration',
    description: 'Get company site configuration records. Call first to discover available fields.',
    inputSchema: {
      type: 'object',
      properties: {
        companyId: {
          type: 'number',
          description: 'The company ID whose site configuration records should be returned'
        }
      },
      required: ['companyId']
    }
  • Tool registered in the 'companies' category of TOOL_CATEGORIES.
    companies: {
      description: 'Search, create, and update companies',
      tools: ['autotask_search_companies', 'autotask_create_company', 'autotask_update_company', 'autotask_get_company_site_configuration', 'autotask_update_company_site_configuration']
    },
  • Dispatch handler that calls autotaskService.getCompanySiteConfigurations(a.companyId) and returns the result.
    ['autotask_get_company_site_configuration', async (a) => {
      const r = await s.getCompanySiteConfigurations(a.companyId);
      return { result: r, message: `Found ${r.length} site configuration record(s) for company ${a.companyId}` };
  • Service method getCompanySiteConfigurations that queries Autotask CompanySiteConfigurations entity filtered by companyID.
    async getCompanySiteConfigurations(companyId: number): Promise<any[]> {
      const http = await this.ensureClient();
      try {
        this.logger.debug(`Getting company site configurations for company ID: ${companyId}`);
        return await http.query<any>(
          'CompanySiteConfigurations',
          [{ op: 'eq', field: 'companyID', value: companyId }],
          { maxRecords: 100 }
        );
      } catch (error) {
        this.logger.error(`Failed to get company site configurations for company ${companyId}:`, error);
        throw error;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool gets records for discovery but does not disclose whether it is read-only, what side effects exist, or what exactly 'discover available fields' means in terms of output. The lack of detail on return format or behavior is a significant gap.

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 efficient sentences that front-load the action and key guidance. No redundant information, earning its conciseness.

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?

Despite the tool being simple, the description fails to explain the output format or what 'site configuration records' entail. Without an output schema, the agent lacks understanding of what the tool returns, and the 'discover fields' hint is vague.

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?

The input schema has 100% description coverage, so the schema already documents the single parameter. The description adds no extra meaning, such as source of the company ID or usage tips, beyond what the schema provides.

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 verb 'Get' and the resource 'company site configuration records', and adds the unique guidance 'Call first to discover available fields', which distinguishes it from other get tools in the sibling list.

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

Usage Guidelines4/5

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

The description explicitly instructs to call this tool first to discover available fields, providing clear usage context. However, it does not mention when not to use it or suggest alternatives among the many sibling tools.

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