Skip to main content
Glama
vectra-ai-research

Vectra AI MCP Server

get_account_details

Retrieve comprehensive security details for a specific Vectra AI account, including detections, scoring, associated accounts, access history, and threat data to analyze potential security risks.

Instructions

    Get complete detailed information about a specific account entity. This tool returns account details including detections, scoring information, associated accounts, access history, detection summaries, external data, and more. Response can be customized using various parameters to include or exclude specific fields and related data.
    
    Returns:
        str: JSON string with detailed information about the account. It includes detections, scoring information, associated accounts, access history, detection summaries, external data, and more.
        If the account is not found, returns a message indicating that no account was found with the specified ID.
        If an error occurs during the request, raises an exception with the error message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesID of the account in Vectra platform to retrieve details for
fieldsNoFields to return in the results. Available fields: id, url, account_type, assignment, associated_accounts, certainty, data_source, detection_set, detection_summaries, last_detection_timestamp, name, note, note_modified_by, note_modified_timestamp, notes, past_assignments, privilege_category, privilege_level, probable_home, sensors, severity, state, tags, threat
exclude_fieldsNoFields to exclude in the response object. Accepts comma-separated list. Available fields: 'id', 'url', 'name', 'state', 'threat', 'certainty', 'severity', 'account_type', 'tags', 'note', 'notes', 'note_modified_by', 'note_modified_timestamp', 'privilege_level', 'privilege_category', 'last_detection_timestamp', 'detection_set', 'probable_home'.
include_access_historyNoInclude account access history in the response
include_detection_summariesNoInclude detection summaries for the detections on the account in the response object.
include_externalNoInclude external data in the response object.
src_linked_accountNoSource linked account filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behaviors: error handling (returns message if account not found, raises exception on request error) and return format (JSON string). However, it doesn't mention authentication requirements, rate limits, performance characteristics, or whether this is a read-only operation (though 'get' 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.

Conciseness3/5

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

The description is reasonably structured with purpose statement followed by return behavior, but contains redundancy (repeating 'detections, scoring information...' in both purpose and returns sections). The 'Returns:' section could be more concise, and some sentences could be tightened for better front-loading of key information.

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

Completeness4/5

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

Given the tool's complexity (7 parameters, detailed retrieval), no annotations, but with 100% schema coverage and an output schema (implied by 'Returns' section), the description provides adequate context. It covers purpose, return format, and error handling, though could benefit from more behavioral context about the operation's characteristics.

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 description coverage is 100%, so the schema already documents all 7 parameters thoroughly. The description adds minimal value beyond the schema - it mentions customization parameters generically but doesn't explain specific parameter interactions or provide additional semantic context. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get complete detailed information about a specific account entity' with specific resources listed (detections, scoring information, associated accounts, etc.). It distinguishes itself from siblings like 'get_host_details' by focusing on accounts rather than hosts, but doesn't explicitly contrast with other account-related tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. While it mentions customization parameters, it doesn't explain when this detailed retrieval is appropriate versus simpler listing tools like 'list_entities' or 'lookup_entity_info_by_name' available in the sibling tool list.

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/vectra-ai-research/vectra-ai-mcp-server'

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