hemmiles-mcp-server

List Hemmiles resources

hemmiles_list_resources

Read-onlyIdempotent

Fetch Hemmiles guides, blog posts, and resources/docs/help hubs by section and locale to discover available pages and their URLs.

Instructions

List Hemmiles resource content: guides, blog posts, and the resources/docs/help hubs, as discovered from the sitemap.

Args:

kind ('all'|'guides'|'blog'|'resources'|'docs'|'help', default 'all').
locale (optional): market whose URLs to return (default: server locale).
response_format ('markdown'|'json').

Returns JSON: { total, count, pages: [{ url, path, section, locale, title? }] }.

Example: "What guides does Hemmiles have?" -> kind='guides'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hemmiles_list_resources"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Which resource section to list: all, guides, blog, resources, docs, or help.	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

Name	Required	Description	Default
`count`	Yes
`pages`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: results are sitemap-derived (implying potential gaps in coverage) and it documents the return payload shape. It omits freshness/caching behavior and any rate-limit notes, keeping it short of a 5.

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, then follows a predictable Args/Returns/Example structure with no filler prose. The Args block duplicates enum values already fully specified in the schema, which is some wasted space, 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.

Completeness4/5

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

For a zero-required-parameter listing tool with an output schema, the description covers purpose, scoping, defaults and an invocation example, so an agent could call it correctly. The missing piece is positioning against hemmiles_list_pages and hemmiles_search_site, which matters given nine sibling tools.

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?

With 100% schema description coverage, the schema already documents all three enums and defaults, and the description largely restates them verbatim. The only added value is the locale parenthetical (default: server locale) and the question-to-kind example, which is marginal beyond the schema.

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 first line states a specific verb and resource ('List Hemmiles resource content') and enumerates the exact sections covered: guides, blog posts, resources/docs/help hubs. It also discloses the source of truth ('as discovered from the sitemap'). It does not explicitly contrast itself with the close sibling hemmiles_list_pages, so differentiation is inferred from the section enumeration rather than stated.

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?

The worked example ('What guides does Hemmiles have?' -> kind='guides') gives concrete guidance on how to translate a user question into a call, and the kind filter defines the scoping choices. There is no explicit when-not-to-use guidance or pointer to hemmiles_list_pages / hemmiles_search_site for broader or keyword-based needs.

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

Deploy Server