vcf-ops-mpb-mcp

List collectors

mpb_list_collectors

Read-only

List VCF Operations collectors and cloud proxies with their UUIDs, providing the collectorId needed for source tests.

Instructions

Lists VCF Operations collectors / cloud proxies with their uuId, which source tests need as collectorId.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the genuinely useful fact that the returned uuId is the collectorId consumed by source tests, but says nothing about result count, ordering, empty results, or what happens when no collectors exist.

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 front-loaded sentence that states the resource, the key returned field, and its downstream purpose with no filler. Every clause earns its place.

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 no parameters and no output schema, the description is the only place an agent can learn the return shape, and it does disclose the uuId field and its meaning. It falls short of fully describing the returned payload (other fields, cardinality) for a tool whose output is otherwise undocumented.

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?

The input schema has zero parameters, so the baseline applies. The description correctly implies the call is unfiltered and global, which matches the empty properties object rather than contradicting it.

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 uses a specific verb ("Lists") on a specific resource ("VCF Operations collectors / cloud proxies") and even resolves the domain alias between the two terms. It never names a sibling to contrast with, so the differentiation is implicit rather than explicit.

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?

It supplies a concrete call-site context: this is where an agent gets the uuId used as collectorId by source tests. That is clear when-to-use guidance, but there is no stated exclusion (e.g., whether it is ever needed outside source configuration) or alternative path.

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