Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_sync_all_sources

Triggers synchronization for all enabled content sources in one call, letting you refresh source data together instead of syncing each source individually.

Instructions

Trigger synchronization for all enabled content sources.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexterm_sync_all_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, and destructive=false, so the mutation/network profile is covered. The description adds that only *enabled* sources are affected, which is meaningful scoping. It does not say whether the call blocks or returns a job handle, how long it runs, or what happens if a sync is already in progress.

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?

A single sentence with zero waste, front-loaded on the action and the scope. Nothing extraneous.

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?

There is no output schema, so the description carries the burden of explaining the return behavior — and it does not say whether this is fire-and-forget, returns a task id, or reports per-source results. For a fan-out trigger tool with openWorldHint=true, that is a notable omission.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description does contribute the 'enabled only' filter semantics, clarifying which sources are in scope without any input.

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?

States a specific verb ('Trigger synchronization') and a clear scope ('all enabled content sources'), which implicitly separates it from the single-source sibling nexterm_sync_source. However, it does not explicitly name or contrast with that sibling or nexterm_sync_integration, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'all enabled content sources' implies this is the bulk/everything variant versus per-source syncing, which is useful context. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., whether to call this instead of nexterm_sync_source).

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