Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Export Configuration

export_configuration
Destructive

Export VBR configuration objects as JSON import specs for documentation, review, migration, or create_object templates; sensitive credential exports require server confirmation.

Instructions

Export VBR configuration objects as JSON import specs - for documentation, review, migration to another VBR server, or as a template for create_object. Exporting credentials / cloud credentials / encryption passwords is confirmed by the server because the output is sensitive.

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": {
      "kind": "<kind>"
    },
    "name": "export_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
filtersNoOptional export spec: {'ids': [...], 'names': [...], 'types': [...]} (see describe_endpoint).
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds genuinely useful behavior beyond the annotations: exporting credentials, cloud credentials, or encryption passwords triggers a server-side confirmation because output is sensitive, which explains the otherwise surprising destructiveHint=true on an export. It does not specify how the confirmation round-trip works or whether the export itself alters server state.

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?

Front-loads the core action in the first clause, then adds use cases and the sensitivity caveat. Roughly 40 words with no filler, though the use-case list and the credentials sentence are slightly compressed into one block.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers purpose, use cases, and the sensitive-kind confirmation path for a 3-parameter tool. Remaining gaps are the exact filter/kind interaction and the confirm-token workflow mechanics.

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 only 33%, so the description should carry more weight than it does. It obliquely explains confirm_token by describing server confirmation for sensitive kinds, but says nothing about how `kind` scopes the export or how filters interact with kind; the filters semantics live only in the schema text.

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 ('Export VBR configuration objects as JSON import specs') and enumerates concrete uses: documentation, review, migration, and template for create_object. It does not explicitly contrast with nearby siblings such as import_configuration, but the output-artifact framing makes the operation unambiguous.

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

Usage Guidelines4/5

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

Gives clear affirmative guidance via four named use cases (documentation, review, cross-server migration, create_object templating). There are no when-not-to-use conditions or explicit alternatives named, so it stops short of full routing guidance.

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