delegate_serviceGrant OPERATOR access to one of YOUR VPS to another person by email (they can power/reinstall/console/hostname/rdns, but NOT renew, cancel or change billing). Sends them an invitation with an accept link. Optional expires_days for time-limited access. Owner-only.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | |||
| service_id | Yes | ||
| expires_days | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description discloses key behaviors: sends invitation link, permissions granted, optional time limit. Could mention revocation possibility but sibling suggests it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with high information density. Front-loaded action, then details and a note on owner-only. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and description does not explain return value, errors, or prerequisites like login. Adequate for basic usage but lacks completeness for a tool with no annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
0% schema coverage is compensated by description explaining email, service_id, and expires_days meaning. Adds context that expires_days is optional and for time-limited access.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states action: granting OPERATOR access to a VPS via email. Lists exact permissions and restrictions, distinguishing from siblings like accept_delegation and revoke_delegation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Owner-only' and that it sends an invitation, guiding when to use. Lacks explicit comparison to accept_delegation or revoke_delegation, but context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are cleanly separated into auth, billing, VPS lifecycle, tickets, and delegation, and each maps to a distinct resource/action. A few pairs like set_password vs reset_password and pay_invoice vs topup_balance share surface similarity, but their descriptions draw clear boundaries.
Naming is strongly consistent with verb_noun snake_case patterns such as order_vps, list_tickets, and revoke_delegation. Minor deviations are the bare CLI-style verbs login and whoami, plus the slightly awkward topup_balance, but these do not undermine the overall pattern.
27 tools is on the high side, but the server covers several distinct subdomains—account management, billing, VPS operations, support tickets, and delegations—and each tool appears to earn its place. The count is heavy but not unreasonable for the breadth of functionality exposed.
Core workflows are covered end-to-end: account creation/login, ordering and provisioning, power/reinstall/cancel, ticket conversations, and delegation management all have the necessary operations. Minor gaps exist, such as no change-password tool, no explicit RDNS/console tool despite delegation mentioning them, and no plan upgrade/downgrade tool.