Skip to main content
Glama
Sign In
Tenable OT Security MCP Server

Tenable OT Security MCP Server

by aqamahn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get a rule group by id

get_rule_group

Retrieve a rule group and its first 25 rules by specifying the group ID.

Instructions

One rule group with the first 25 included rules.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "get_rule_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that only the first 25 included rules are returned, which is a useful behavioral trait, but it does not cover error handling, permissions, or the full response structure.

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?

The description is extremely short but is a fragment rather than a complete sentence. It under-specifies the tool's behavior, and while there are no wasted words, it sacrifices necessary clarity for brevity.

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?

With one parameter, no annotations, and an output schema not shown, the description should provide more context. It only mentions the 25-rule limit, omitting the tool's overall purpose, parameter guidance, or any usage context, leaving it incomplete for an agent to confidently invoke.

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?

The schema has one parameter, group_id, with no description and 0% schema description coverage. The description does not mention group_id or explain what a rule group ID is or how it is used, failing to compensate for the schema gap.

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 'One rule group with the first 25 included rules' is a noun phrase without an explicit verb, though it clearly implies returning a single rule group. It adds a distinguishing detail about the 25-rule limit but relies heavily on the tool name and title for context.

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 is provided on when to use get_rule_group versus alternatives like list_rule_groups or get_tag_group. The description lacks any context about selection criteria, prerequisites, or exclusionary conditions.

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