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 tag group by id

get_tag_group

Retrieve a tag group by its ID to view up to 100 member items, supporting OT asset organization and filtering.

Instructions

One tag group with up to 100 member items.

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_tag_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

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses a meaningful behavioral constraint ('up to 100 member items'), which helps set expectations. However, it does not mention error handling, access permissions, or behavior for non-existent IDs.

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?

The description is a single, compact sentence that conveys the essential scope and a key limit. Every word earns its place; no fluff or redundancy.

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?

For a simple get-by-id tool with one parameter and an output schema, the description is adequate but not complete. It highlights the 100-item limit but omits potential edge cases like archived groups or what happens when a group has more than 100 members, leaving the agent to infer behavior.

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 description does not explain the group_id parameter beyond what the schema already provides (a string titled 'Group Id'). With 0% schema description coverage, the description should compensate, but it adds no parameter-specific meaning.

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 title 'Get a tag group by id' provides the verb and resource, and the description adds that it returns one tag group with up to 100 member items. This distinguishes it from list_tag_groups, which returns multiple groups, though the description itself lacks an explicit verb.

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?

The description gives no guidance on when to use this tool versus alternatives like list_tag_groups or get_port_group. There is no mention of prerequisites, exclusions, or preferred scenarios.

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