hemmiles-mcp-server

Get Hemmiles contact & demo options

hemmiles_get_contact_options

Read-onlyIdempotent

Get official Hemmiles contact options, including demo request, contact page, and support email, to reach sales or support when no online checkout is available.

Instructions

Return the official, supported ways to engage with Hemmiles: the sales/demo request page, the general contact page, and the support email — assembled from the site's Organization contact points and known pages.

Why this instead of cart/checkout: Hemmiles has no online store, cart, or self-serve checkout, so the brief's add_to_cart / get_cart / remove_from_cart / create_checkout_link tools are not implemented. This tool is the safe, legitimate alternative — it only returns official links and never performs any transaction or submits any form.

Args:

locale (optional): market prefix for the page links (default: server locale).
response_format ('markdown'|'json').

Returns JSON: { email?, demoUrl, contactUrl, pricingUrl, salesContactUrl?, note }.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Market locale/region. One of: global, in, us, gb, ca, au, nz, ie, sg, ae, za. 'global' uses the locale-less canonical pages. Defaults to the server's configured locale.
`response_format`	No	Output format: 'markdown' (human-readable) or 'json' (structured).	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`email`	No
`demoUrl`	Yes
`contactUrl`	Yes
`pricingUrl`	Yes
`salesContactUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses that it only returns official links, never performs transactions, and never submits forms. It also explains that results are assembled from Organization contact points and known pages, adding useful provenance.

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 front-loaded with purpose and includes a useful rationale for the cart/checkout alternative. It is somewhat verbose in repeating return fields and argument details already covered by structured data.

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?

Given the rich annotations, full schema coverage, and an output schema, the description supplies everything needed: purpose, alternative context, safety behavior, parameters, and return fields. No material gap remains for an agent selecting or invoking it.

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 the schema already fully documents locale and response_format. The description repeats their meaning but adds little parameter-specific detail beyond what the schema provides.

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: returning Hemmiles' official sales/demo, contact, and support email options. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as hemmiles_get_company_info or hemmiles_get_policies.

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 clear usage context by positioning the tool as the legitimate alternative to cart/checkout tools that do not exist for Hemmiles. It does not, however, explain when to choose this over the many Hemmiles informational siblings.

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

Deploy Server