Skip to main content
Glama
Sign In
vhe-deploy-mcp

vhe-deploy-mcp

by herlonventura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_sites

Read-onlyIdempotent

Lists registered domains and sites available for deployment management, without requiring passwords or an active SFTP/FTPS connection.

Instructions

Lista os domínios cadastrados, sem senhas ou conexão.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
messagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds behavioral context by stating that the result excludes passwords and connection information, which is useful for agents expecting credentials. No contradiction.

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?

One short sentence in Portuguese that front-loads the action and includes the key exclusion. Every word earns its place with no redundancy.

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?

For a parameterless listing tool with an output schema and annotations covering safety, the description is fully sufficient. It clarifies the returned resource (domains) and what is excluded (passwords, connection), leaving no critical gap for an agent to call it correctly.

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?

There are no parameters (0), so the schema already covers everything. The description adds nothing about parameters because none exist. Baseline 4 is appropriate.

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?

The description states 'Lista os domínios cadastrados' (lists registered domains) and adds 'sem senhas ou conexão' (without passwords or connection), making the action and resource explicit. It is clearly distinct from siblings like deploy_site or test_connection.

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: it lists domains. However, it does not explicitly state when to use this over alternatives or mention any exclusions beyond what it lists. Given the sibling set, more explicit routing would help, but the purpose is self-evident.

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

Deploy Server

Other Tools