Skip to main content
Glama
Sign In
hostwares-mcp

hostwares-mcp

by Hostwares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ask

Ask questions or make requests to the Hostwares AI DevOps assistant for deploying sites, managing databases, and troubleshooting deployments.

Instructions

Ask the Hostwares AI DevOps assistant anything

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

Input Schema

NameRequiredDescriptionDefault
messageYesYour question or request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Ask anything' without disclosing limitations, whether it can perform actions, response format, or any restrictions (e.g., scope of knowledge, rate limits). This is insufficient for an AI agent to understand expected 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?

The description is a single concise sentence with no wasted words. It could benefit from additional structure (e.g., hints on phrasing questions), but it is appropriately sized for a simple tool.

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 one parameter and no output schema, the description is functional but minimal. It does not explain the return value or confirm that the assistant will provide an answer. Given the simplicity, it's adequate but not robust.

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?

Only one parameter 'message' with schema description 'Your question or request'. The tool description adds 'Ask the Hostwares AI DevOps assistant anything' which reinforces that the message is a query, but does not add new semantic detail beyond the schema. With 100% schema coverage, baseline is 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 clearly states the tool is for asking the Hostwares AI DevOps assistant anything, which is a specific verb and resource. However, it could be more precise about the scope of questions (e.g., 'about your Hostwares account and deployments') to distinguish it from sibling tools that are action-oriented.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description implies it's for questions, but does not explicitly state that for performing actions, users should use sibling tools like deploy_site or get_deployment_logs.

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