Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Describe Model

describe_model
Read-onlyIdempotent

Returns a named VBR API model schema with fields, required properties, enum values, descriptions, and polymorphic subtype variants so you can inspect object structure before write operations.

Instructions

Schema of one VBR API model by name (e.g. EntireCloudDirectorVMCustomizedRestoreSpec, VmwareObjectModel).

Shows fields, which are required, enum values and descriptions; x-subtypes lists the concrete variants of a polymorphic model.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
depthNo

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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description usefully adds what the response contains (fields, required flags, enums, descriptions, x-subtypes). It does not disclose anything about the `depth` parameter's behavior or response size, which is the main unannotated behavior an agent would want.

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 tight sentences, front-loaded with the verb and resource, with no filler. The second sentence is a dense but purposeful enumeration of returned content.

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?

Annotations cover safety and the description covers return content in lieu of an output schema, so the basics are present. For a two-parameter schema tool, the unexplained `depth` parameter is a real completeness gap that an agent cannot resolve from structured data.

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%, so the description must carry the parameter burden. It compensates well for `name` by giving concrete examples, but the `depth` parameter (integer, default 2, range 0-4) is never mentioned, leaving a key control — presumably schema recursion depth — completely unexplained.

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?

Names a specific resource ('one VBR API model') and the operation (returns its schema), with concrete example model names that make the concept tangible. It does not explicitly differentiate itself from sibling `describe_endpoint`, so it stops short of a 5.

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?

Usage is implied rather than stated: the agent learns it needs a model name and sees example names, which is enough to know when the tool applies. There is no explicit when-not guidance and no named alternative (e.g. describe_endpoint) for the adjacent case.

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