Skip to main content
Glama
Sign In
threatlocker-mcp

threatlocker-mcp

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

maintenance_mode_get_by_computer_id

Retrieve the maintenance schedule for a specific computer by its ID. Use this to view or verify when maintenance is scheduled for a computer without making manual checks.

Instructions

Get Maintenance Schedule By Computer Id

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

Input Schema

NameRequiredDescriptionDefault
computer_idNo
organization_idNoOverride the default organization (ManagedOrganizationId header).
override_organization_idNoOptional OverrideManagedOrganizationId header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' implying a read operation, but does not disclose authorization requirements, behavior when computer_id is null or not found, or any side effects. The minimal description leaves significant ambiguity.

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 a single sentence with no waste, but it is so concise that it omits essential context. It could benefit from a slightly longer structure that adds value without verbosity.

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?

No output schema is provided, and the description does not hint at the return format or structure. With three parameters (none required), the agent lacks guidance on required inputs (computer_id likely needed) and expected output. Incomplete for effective tool invocation.

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?

The input schema covers 67% with descriptions for organization_id and override_organization_id, but the description adds nothing beyond the parameter names. The key parameter computer_id lacks schema description and the tool description does not clarify its role, default, or whether it is required.

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 'Get Maintenance Schedule By Computer Id', specifying the verb (get) and resource (maintenance schedule by computer ID). However, it does not distinguish from potential sibling retrieval tools, but given the sibling list, this is the only get tool for maintenance mode by computer ID, so it is sufficiently clear.

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. Sibling tools include computer_update_maintenance_mode, maintenance_mode_end_by_id, maintenance_mode_insert, etc., but the description does not indicate that this is the read-only retrieval tool or provide any 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

Other Tools