Skip to main content
Glama
Sign In
threatlocker-mcp

threatlocker-mcp

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

approval_request_get_by_id

Get an approval request by ID. The requestor reason is base64-encoded—decode before displaying.

Instructions

Get Approval Request By ID NOTE: requestorReason is base64-encoded -- decode before display. approval_request_get_permit_application_by_id returns the same request with the reason already decoded under fileDetails.requestorReason, plus file/policy/ringfencing context.

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

Input Schema

NameRequiredDescriptionDefault
approval_request_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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that requestorReason is base64-encoded and needs decoding, a key behavioral trait. It does not mention potential errors or authentication, but the disclosure is good for a simple get tool.

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

Conciseness5/5

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

Two concise sentences with front-loaded key info. Every sentence adds value; no fluff.

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

Completeness3/5

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

Given no output schema, the description could do more. It addresses the quirk and alternative but omits response structure, pagination, or rate limits. Adequate but not rich.

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 coverage is 67%, with approval_request_id lacking description. The description adds no parameter details beyond the schema. The primary parameter is not explained, and its optionality with default null is confusing.

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

Purpose5/5

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

The description explicitly states the tool retrieves an approval request by ID, with a note about base64 encoding. It distinguishes itself from a sibling tool (approval_request_get_permit_application_by_id) that returns decoded data and more context.

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

Usage Guidelines5/5

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

The description provides clear guidance on when to use this tool versus the alternative: use this for raw, base64-encoded requestorReason; use the sibling for decoded reason and additional context.

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