Skip to main content
Glama
Sign In
tie-mcp-server

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_profile

Update a Tenable Identity Exposure profile by specifying its ID and providing new values for name, deletion status, or directories.

Instructions

Update profile instance.

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter: id
bodyYesProfile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The description uses 'Update' which implies mutation, but fails to disclose behavioral traits such as side effects, required permissions, or what happens on success/failure. With no annotations provided, the description carries full burden but offers minimal behavioral insight.

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?

While the description is short (one sentence), it is too minimal to be useful. It does not earn its place as it provides no actionable information beyond the tool name. Front-loading is absent.

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

Completeness1/5

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

Given the tool has a nested object, required parameters, no output schema, and no annotations, the description is critically incomplete. It fails to describe return values, error conditions, or the effect of the update, leaving the agent with insufficient context.

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

Parameters3/5

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

Schema coverage is 100% and the description adds no extra meaning beyond what the input schema provides. It does not explain the purpose of the parameters or their constraints (e.g., pattern on 'name' or minimum/maximum on 'directories'). Baseline 3 is appropriate.

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 'Update profile instance' clearly indicates the verb 'Update' and the resource 'profile instance'. However, it lacks specificity about which fields can be updated, and given many sibling tools like 'create_profile' and 'clone_profile', it does not distinguish itself beyond the generic action.

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 alternatives like 'clone_profile' or 'commit_profile'. No prerequisites, exclusions, or contextual hints provided. The description is too brief to convey usage 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