Skip to main content
Glama

vibedeploy

by be.vibedeploy
OverviewDiscussionsAdmin

List DNS records for a site

list_dns_records
Read-onlyIdempotent

Read the DNS records VibeDeploy tracks for a site (the records it created/manages on your behalf), oldest first. Returns each record's host, type, and value. Any team member, including viewers, can read DNS records. This tool is read-only and does NOT create, change, or delete any DNS record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSite name to look up DNS records for.
siteIdNoSite id to look up DNS records for. Provide name or siteId.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
siteIdYes
recordsYesDNS records VibeDeploy tracks for this site, oldest first. Read-only — DNS changes are not made through this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}
  2. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark readOnly, idempotent, and non-destructive, and the description reinforces this by stating it does NOT create, change, or delete DNS records. It adds useful context about viewer permissions, ordering (oldest first), and the managed subset of records VibeDeploy tracks.

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?

Three sentences with no filler: scope, return content/order, permissions, and read-only behavior are all covered. Every sentence contributes useful information.

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

Completeness5/5

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

The tool has rich annotations, a complete input schema, and an output schema, so the description only needs to add behavioral context. It covers ordering, scope of records, permissions, and non-mutating behavior, which is sufficient for correct invocation.

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?

Both parameters are fully described in the input schema (name and siteId), so schema coverage is 100%. The description adds no additional parameter-level meaning beyond the schema, earning the baseline score of 3.

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 and resource ('Read the DNS records VibeDeploy tracks for a site') and clearly scopes to records created/managed on the user's behalf. It is clear but does not explicitly differentiate from sibling tools like list_custom_domains, 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 Guidelines4/5

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

The description makes the read-only context clear and states that any team member, including viewers, can use it. However, it does not explicitly say when to prefer this over related domain/DNS tools, so there are no exclusions or alternatives named.

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

All vibedeploy toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources