threatlocker-mcp

action_log_get_by_id_v2

Retrieves a specific action log entry by its ID. Supports options to include parent entries or add the entry to an application.

Instructions

Action Log: Get By Id V2

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "action_log_get_by_id_v2"
  }
}

Input Schema

Name	Required	Description
`e_action_log_id`	No
`source_table_id`	No
`add_to_application`	No
`get_all_parents`	No
`opened_from_link`	No
`organization_id`	No	Override the default organization (ManagedOrganizationId header).
`override_organization_id`	No	Optional OverrideManagedOrganizationId header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 14, 2026

TDQS

D1/5.0

Behavior1/5

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

No annotations and description does not disclose any behavioral traits such as read-only nature, side effects, or error behavior.

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

Conciseness1/5

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

Extremely brief but underspecified; lacks necessary information for tool usage, so not appropriately sized.

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

Completeness1/5

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

With 7 parameters and no output schema, description is severely lacking; does not explain return values or behavior.

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

Parameters1/5

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

Schema has 7 parameters with only 2 having descriptions (29% coverage). Description adds no meaning to parameters beyond schema.

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

Purpose1/5

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

Description is 'Action Log: Get By Id V2', which is a tautology and does not specify what the tool does. It does not distinguish from siblings like action_log_get_by_parameters_v2.

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

Usage Guidelines1/5

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. No context provided.

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

Deploy Server