Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_sync_integration

Synchronizes an existing Nexterm integration by integration ID to keep connected server records up to date.

Instructions

Synchronize an existing Nexterm integration.

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": {
      "integration_id": "<integration_id>"
    },
    "name": "nexterm_sync_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
integration_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, open-world operation, so the description need not repeat that. The description adds only the precondition that the integration must be 'existing'; it does not explain what synchronization changes, whether it contacts an external system, whether it can fail partially, or what the agent should expect afterward.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted words. However, its extreme brevity leaves important behavioral and usage details unstated, so it is concise but arguably under-specified rather than optimally structured.

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 mutation/synchronization tool with an open-world hint and no output schema, the description is too thin. It does not say what synchronization does, whether it is asynchronous, what permissions are needed, or what observable effect the call has, leaving the agent to infer critical 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?

Schema description coverage is 0% for the single required parameter, integration_id, and the description does not mention it at all. Saying 'an existing Nexterm integration' weakly implies the parameter identifies the target, but it adds no meaning about the expected value, format, or how to obtain a valid integration ID.

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: 'Synchronize an existing Nexterm integration.' An agent can tell this is an integration-level sync operation, but it does not distinguish it from sibling tools like nexterm_sync_source or nexterm_sync_all_sources, nor explain what 'synchronize' means in this 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?

There is no guidance on when to use this tool versus alternatives such as nexterm_get_integration, nexterm_delete_integration, nexterm_sync_source, or nexterm_sync_all_sources. The only implied condition is that the integration must already exist, but no prerequisites, exclusions, or alternatives are stated.

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