nexterm-mcp

Overview Schema Source Related Servers Discussions Admin

nexterm_update_organization_audit_settings

Updates audit settings for an organization to enable or disable session recording, set retention days, and control auditing across AI, file, script, folder, server, and identity operations.

Instructions

Update audit settings for an organization.

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": {
      "organization_id": "<organization_id>"
    },
    "name": "nexterm_update_organization_audit_settings"
  }
}

Input Schema

Name	Required	Description	Default
`organization_id`	Yes
`enable_session_recording`	No
`recording_retention_days`	No
`enable_ai_operation_audit`	No
`require_connection_reason`	No
`enable_file_operation_audit`	No
`enable_script_execution_audit`	No
`enable_folder_management_audit`	No
`enable_server_connection_audit`	No
`enable_server_management_audit`	No
`enable_identity_management_audit`	No
`enable_identity_credentials_access_audit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 29, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the safety profile is covered. The description adds nothing beyond that: it does not explain partial-update behavior, whether omitted/null fields are left untouched, whether all settings are overwritten, or what permissions are needed for a 12-parameter mutation.

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

Conciseness3/5

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

A single efficient sentence with no filler, but that brevity comes at the cost of under-specification rather than earned concision.

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?

For a 12-parameter mutation with no output schema and zero schema-level descriptions, one sentence is far too thin. An agent knows what resource it touches but not how to construct a safe call or what the result will be.

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 description coverage is 0% across 12 parameters, so the description must compensate and does not. The critical ambiguity — whether a null default means 'leave unchanged' or 'disable', and the difference between null and false for the ten boolean flags — is left entirely unexplained, though the parameter titles are self-descriptive.

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 states a specific verb and resource ('Update audit settings for an organization'), making the operation unambiguous. It does not distinguish this from the obvious sibling `nexterm_get_organization_audit_settings`, but the verb/resource pair is clear enough on its own.

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?

There is no guidance on when to use this versus the read sibling `nexterm_get_organization_audit_settings`, and no mention of prerequisites such as admin permissions or the need to inspect current settings first. Usage is only inferable from the name.

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

Deploy Server