threatlocker-mcp

online_devices_get_by_parameters

Retrieve a paginated list of online devices by specifying organization ID, page number, and page size.

Instructions

View Online Devices

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": "online_devices_get_by_parameters"
  }
}

Input Schema

Name	Required	Description
`page_number`	No
`page_size`	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

C2.2/5.0

Behavior2/5

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

No annotations provided. Description only says 'View Online Devices', omitting any behavioral traits such as read-only nature, pagination behavior, authentication needs, or rate limits.

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

Conciseness2/5

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

Single sentence 'View Online Devices' is under-specified, not concise. It lacks essential information and fails to justify its brevity with completeness elsewhere.

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 4 parameters, no output schema, and no annotations, the description is highly incomplete. It does not explain pagination, filtering, or the meaning of 'online devices', making it inadequate for agent use.

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

Parameters2/5

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

Schema description coverage is 50% (two parameters have descriptions in schema). Tool description adds no additional meaning to any parameter. It does not compensate for the parameters lacking schema descriptions.

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

Purpose3/5

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

Description states 'View Online Devices' which gives a verb and resource, but is vague about what constitutes an 'online device'. It distinguishes from siblings by name but lacks specificity.

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?

No guidance on when to use this tool versus alternatives like other get_by_parameters tools. No context on prerequisites or typical use cases.

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

Deploy Server