Argus Customer MCP Tools¶
These tools let the LLM retrieve Argus customer information and customer-specific properties from the customer API.
They support two common tasks:
- list Argus customers and their identifiers
- fetch properties for one customer by customer ID or short name
General Notes¶
- Use these tools when you want the LLM to find Argus customer IDs, short names, or customer properties.
- Customer IDs and short names are commonly needed by other Argus tools, such as case, event, asset, and datastore requests that require a customer scope.
- Customer property lookup accepts either a customer ID or a short name. The LLM can use the customer listing first when it needs to resolve a human-readable customer name to the identifier expected by Argus.
- Tool results are live Argus API results. The LLM should treat them as the source of truth and not infer missing customer values.
Tool: executeFetchArgusCustomer¶
Purpose
Retrieve Argus customer information, including customer IDs and short names the LLM can use in other Argus workflows.
Arguments
This tool takes no arguments.
Result Notes
- Results include Argus customer identifiers and short names.
- The tool uses its built-in customer listing request. It does not expose customer search filters, sorting, pagination, or property-selection arguments.
- When you ask about cases, events, assets, or datastore entries for a named customer, the LLM can use this tool to resolve the customer value behind the scenes before using another Argus tool.
Tool: getCustomerProperties¶
Purpose
Fetch properties for a specific Argus customer. The customer can be identified by either customer ID or short name.
Arguments
| Field | Description | Type | Default | Required |
|---|---|---|---|---|
idOrShortname |
Argus customer ID or short name identifying the customer whose properties should be fetched. | string |
None | Yes |
Usage Notes
- Use this tool when the question needs customer metadata or customer-specific properties rather than just the customer ID and short name.
- If the user gives a customer name that may not be the exact short name, the LLM can first retrieve the customer list and choose the matching customer identifier.
- The value should identify one customer. Ambiguous customer references should be clarified or resolved from the customer list before fetching properties.