Skip to main content
Glama

EuroVPS

Request a quote from EuroVPS

request_quote

Sends a quote request to the EuroVPS sales engineers on behalf of the person you act for. Only use it when that person asked you to, with their real contact details and their permission to share them. An engineer replies to the email address given. The request is marked as sent by an AI agent.

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": {
      "product": "<product>",
      "name": "<name>",
      "email": "<email>",
      "company": "<company>",
      "message": "<message>",
      "consent": "<consent>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person requesting the quote.
agentNoOptional name of the AI agent or assistant sending this.
emailYesTheir work email; the reply goes here.
phoneNoOptional phone number.
budgetNoOptional monthly budget or range.
companyYesTheir company or organisation.
consentYesMust be true: the person asked you to send this and agreed to share their details with EuroVPS.
messageYesThe workload and requirements: what runs, size, location, timing, current provider.
productYesProduct code from list_services; use "unsure" if unclear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint=true, readOnlyHint=false), the description discloses what the annotations cannot: a human engineer replies to the supplied email, and the request is marked as sent by an AI agent. It does not say whether the request can be retracted or rate-limited, but the key downstream consequence — an external human contact — is made clear.

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, front-loaded with the action, then the consent gate, then the downstream effect. No filler and no repetition of schema content.

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

Completeness4/5

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

For a 9-parameter outbound request tool with no output schema, the description covers the essential unknowns: consent requirement, reply destination, and AI-agent marking. Only minor gaps remain (retraction, expected response time), which are not critical to invoking it correctly.

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%, so every parameter including the product enum and consent constraint is already documented in the schema. The description reinforces that the email is where the reply lands and that details must be the person's real ones, but adds no new syntax or format meaning beyond the schema. Baseline 3 applies.

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 states a specific verb and resource: it 'sends a quote request to the EuroVPS sales engineers' on behalf of a represented person. That is unambiguous and clearly distinct from list_services, though the description itself never names the sibling or routes the agent there (that hint lives only in the product param schema).

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?

It gives an explicit precondition: 'Only use it when that person asked you to, with their real contact details and their permission to share them,' which functions as a when-not-use exclusion for unrequested or fabricated submissions. It does not mention any alternative path (e.g., list_services first to pick a product), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources