Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Get Server Certificate

get_server_certificate
Read-onlyIdempotent

Fetches a server's TLS certificate thumbprint or SSH fingerprint for use in managed server specs before creating objects. Read-only; changes nothing in VBR.

Instructions

Fetch a server's TLS certificate thumbprint or SSH fingerprint - needed in the spec when adding a managed server with create_object(kind='managed_server'). Read-only (changes nothing in VBR).

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": {
      "server_name": "<server_name>",
      "type": "<type>"
    },
    "name": "get_server_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
typeYes
server_nameYes
credentials_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description largely repeats that ('Read-only (changes nothing in VBR)'). It does add genuine workflow context (the value goes into a create_object spec), but says nothing about authentication to the target host, credentials_id requirements, whether the call contacts the remote server, or failure behavior.

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 tightly written sentences with the purpose front-loaded and the usage trigger second — good ordering. The parenthetical 'Read-only (changes nothing in VBR)' partially duplicates the annotations and is the only near-wasteful element.

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?

For a tool with 0% schema coverage and no output schema, the description should explain the parameters and the shape of the returned value (thumbprint vs. fingerprint, by host type). It gestures at the return concept but leaves the agent to guess how to supply credentials and what exactly comes back.

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% across four parameters, so the description carries the full burden and does not meet it. Neither server_name, port, credentials_id, nor the meaning of the 13-value type enum is explained; notably credentials_id (a UUID) is completely opaque, and port's default behavior is left to inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch a server's TLS certificate thumbprint or SSH fingerprint') and even clarifies the output varies by host type. An agent can immediately distinguish this from siblings like create_object or api_read without opening the schema.

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?

Explicitly names the triggering workflow: it is needed when adding a managed server via create_object(kind='managed_server'). It does not state when this tool is *not* appropriate or what to do if the certificate lookup fails, but the positive usage trigger is unambiguous and routes the agent correctly.

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