Skip to main content
Glama
Sign In
threatlocker-mcp

threatlocker-mcp

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

computer_group_get_dropdown_by_organization_id

Get a dropdown list of computer groups for a specific organization ID to populate selection menus.

Instructions

Get Computer Groups by OrganizationId

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

Input Schema

NameRequiredDescriptionDefault
computer_group_o_s_type_idNo
computer_o_s_typeNo
hide_globalsNo
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.2/5.0
Behavior1/5

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

No annotations are provided, and the description adds no behavioral details such as whether the tool requires authentication, returns a limited set, or has side effects. The description is insufficient for safe invocation.

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 extremely brief, which is concise but at the expense of informativeness. It could be expanded with key details without becoming verbose.

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?

Given the number of parameters (5) and the lack of an output schema, the description does not explain what the tool returns or how the parameters affect results. Sibling tools suggest a variety of group-related operations, but this tool's specific output is unclear.

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 40%, with only organization_id and override_organization_id having descriptions. The main description adds no additional meaning beyond the tool name; it does not explain parameters like computer_group_o_s_type_id, computer_o_s_type, or hide_globals.

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?

The description states the verb 'Get' and resource 'Computer Groups' with a filter 'by OrganizationId', but does not clarify what 'dropdown' means in the context, leaving ambiguity about the return format (e.g., a list for a UI dropdown). Among siblings, some also fetch groups, but this tool is moderately distinct.

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 siblings like computer_group_get_group_and_computer or tag_get_dropdown_options_by_organization_id. No context about prerequisites or alternatives, leaving the agent to infer usage.

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