Skip to main content
Glama
Sign In
ukraine.com.ua MCP

ukraine.com.ua MCP

by sanyo4ever
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

adm_hosting_webapp_info

Retrieve systemd and startup information for a hosting site by specifying the host ID.

Instructions

Get web application systemd/startup information for a hosting site host

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

Input Schema

NameRequiredDescriptionDefault
host_idYesHosting host ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states the action without disclosing behavioral traits like side effects, authentication needs, or error behavior (e.g., invalid host_id).

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, clear sentence. It is appropriately short given the tool's simplicity, though it could potentially include return type hints without waste.

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, no output schema, and no annotations, the description is adequate but lacks detail on what the returned information contains (e.g., status, configuration keys). More context would improve completeness.

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?

Schema description coverage is 100% for the single parameter 'host_id', which has a clear description. The tool description does not add meaning beyond that, so baseline 3 applies.

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 clearly states the specific action ('Get web application systemd/startup information') and the resource ('a hosting site host'). It distinguishes from siblings like adm_hosting_sites (general site info) and adm_get_services (services).

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. While the purpose implies usage for web app startup info, there is no explicit when/when-not or mention of sibling tools.

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