Skip to main content
Glama
knethteo

Tenable Identity Exposure MCP Server

by knethteo

tie_resource_action

Create, list, get, update, or delete Tenable Identity Exposure resources like directories, attacks, and users.

Instructions

Perform CRUD operations on a TIE resource.

Args: resource: Resource name from tie_catalog (e.g. "directories", "attacks", "users"). action: Operation — list, get, create, update, or delete. id: Resource ID for get/update/delete operations. body: Request body for create/update operations. params: Optional query parameters (e.g. pagination, filters).

Examples: List all directories: resource="directories", action="list" Get directory #5: resource="directories", action="get", id=5 List recent attacks: resource="attacks", action="list", params={"page": 1} Create a user: resource="users", action="create", body={...} Delete an alert: resource="alerts", action="delete", id=42

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bodyNo
actionNolist
paramsNo
resourceYes
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It does not mention that create/update/delete are destructive, required permissions, or error handling. The example for delete lacks warning, and the impact of invalid resource names is omitted.

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 concise, well-structured with Args and Examples sections, and front-loads the purpose. Every sentence is informative, with no 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?

Given no output schema and multiple resource/action combinations, the description covers parameter usage thoroughly but lacks details on return format, error handling, and pagination specifics. It is adequate but incomplete for a generic CRUD tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description adds significant value by explaining each parameter (resource, action, id, body, params) with examples. It clarifies usage beyond the schema's type definitions, though the format for params is not fully detailed.

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 the tool performs CRUD operations on TIE resources, with examples listing specific resources. It distinguishes from sibling tools which are resource-specific, but does not explicitly highlight its generic nature.

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 tie_alerts or tie_attacks. The description provides examples but does not indicate prerequisites, context, or alternatives for specific resource operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/knethteo/tenable-identity-exposure-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server