hemmiles-mcp-server

Get Hemmiles FAQs

hemmiles_get_faqs

Read-onlyIdempotent

Retrieves published FAQs from a Hemmiles page, including pricing, billing, trial, and user-minimum questions, returning structured question-answer pairs.

Instructions

Return the frequently-asked-questions published on a Hemmiles page, parsed from its FAQPage JSON-LD. The pricing page in particular carries detailed FAQs (billing, user minimums, trials, etc.).

Args:

path (string, default 'pricing'): page to read FAQs from (path or full URL).
locale (optional): market prefix for a bare path.
response_format ('markdown'|'json').

Returns JSON: { url, total, faqs: [{ question, answer }] }.

Example: "What are Hemmiles' pricing FAQs?" -> path='pricing'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No	Page to read FAQs from (default 'pricing'); a path or full hemmiles.com URL.	pricing
`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
`url`	Yes
`faqs`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world semantics, so the description adds context on data provenance (parsed from JSON-LD) and the return shape. It does not mention behavior when a page lacks FAQ markup, which is the one remaining disclosure gap.

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?

Purpose is front-loaded, followed by args and a return shape and example. Slight redundancy between the description's args block and the schema, but nothing is wasted or padded.

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?

With an output schema, rich annotations, and full param coverage, the description covers what an agent needs to call it. Only the empty/no-FAQ-result case is unaddressed, a minor omission given the structured richness.

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 all three parameters are already documented. The description restates path and locale semantics ('market prefix for a bare path') with little that isn't in the schema, meriting the baseline 3.

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+resource ('Return the frequently-asked-questions published on a Hemmiles page') and names the parsing source (FAQPage JSON-LD), which distinguishes it cleanly from siblings like get_page, get_pricing, and 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?

Gives concrete usage context (pricing page carries detailed billing/user-minimum/trial FAQs) and a worked example mapping a natural question to path='pricing'. It stops short of naming alternatives or stating when to prefer get_page over this tool.

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

Deploy Server