Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Rescan Managed Servers

rescan_managed_servers

Rescan multiple managed servers at once, or all managed servers when IDs are omitted, to refresh their state and return a rescan session.

Instructions

Rescan several managed servers at once, or all of them when managed_server_ids is omitted. Returns a session.

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": "rescan_managed_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_tokenNo
managed_server_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so safety is mostly covered. The description adds that the call returns a session, which signals asynchronous job semantics beyond the annotations. It does not explain what confirm_token guards against or whether a rescan disrupts running server operations.

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?

Two short sentences, front-loaded with the action and scope, with no filler. Brevity is earned here, though the second sentence about returning a session could have been folded in more usefully.

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?

An output schema exists, so return values need not be detailed, and the description is adequate for a zero-required-parameter bulk action. However, for a mutating-with-side-effects style operation it omits the confirm_token contract and any note on the effect of rescanning all servers at once.

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 coverage is 0%, so the description must carry parameter meaning. It does explain the null/omitted behavior of managed_server_ids well, but confirm_token is completely unaddressed despite being an opaque name that strongly implies a confirmation/guard step.

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 and resource ('Rescan several managed servers') and gives the scope rule (several at once, all when managed_server_ids is omitted). That resource framing is enough to separate it from siblings like rescan_replicas or rescan_inventory, though it never names them.

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 only guidance is the omission rule for managed_server_ids (omit to rescan all), which implies a bulk-vs-targeted decision. There is no statement of when to prefer this over the per-object rescan siblings, and no prerequisites or warnings about rescanning everything at once.

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