hemmiles-mcp-server

Get Hemmiles policies

hemmiles_get_policies

Read-onlyIdempotent

Retrieve available Hemmiles policy pages—security, privacy, terms, legal, and cookies—with summaries by topic and locale; missing policies are reported as unavailable.

Instructions

Fetch Hemmiles' publicly available policy pages (security, privacy, terms, legal, cookies) and return their summaries.

Important: Hemmiles is a digital SaaS subscription, so there is NO shipping policy and NO product return/refund policy in the e-commerce sense (the brief's get_shipping_information / get_return_policy do not apply). Billing, trial, and cancellation terms are covered by pricing FAQs (hemmiles_get_faqs) and the terms page when present. This tool reports only the policy pages that actually exist; missing ones are listed as unavailable.

Args:

topic ('all'|'security'|'privacy'|'terms'|'legal'|'cookies', default 'all').
locale (optional): market prefix (falls back to the global page if the localized one is absent).
response_format ('markdown'|'json').

Returns JSON: { note, found: [{ topic, url, title, description, excerpt }], unavailable: string[] }.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	Which policy to fetch.	all
`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
`found`	Yes
`unavailable`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: only pages that actually exist are reported, missing ones are surfaced in an 'unavailable' list, and locale lookup falls back to the global page.

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?

Front-loads the purpose and the important negative scope before the argument details. Some redundancy between the Args block and the schema, and the reference to 'the brief' is meta, but overall it is tight and scannable.

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?

Output schema exists and the description still summarizes the return shape (note, found entries with url/title/description/excerpt, unavailable list), so an agent knows exactly what to expect. Nothing about invocation or failure modes is left unclear.

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 coverage is 100% with three enums, so the schema already fully documents topic, locale, and response_format. The description's Args block largely restates those enums and the locale fallback rule that the schema already states, adding only the 'all' default framing.

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?

States a specific verb and resource ('Fetch Hemmiles' publicly available policy pages') and enumerates the exact topic set, which distinguishes it from siblings like hemmiles_get_page and hemmiles_list_pages. It also routes the agent away from irrelevant policy types by declaring what does not exist.

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

Usage Guidelines5/5

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

Explicitly says the e-commerce shipping and return policy tools do not apply, and names hemmiles_get_faqs as the alternative for billing, trial, and cancellation terms. That is both a when-to-use and a when-not-to-use with a named sibling.

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

Deploy Server