hemmiles-mcp-server

Get Hemmiles company info

hemmiles_get_company_info

Read-onlyIdempotent

Get Hemmiles' public company and contact information—such as name, website, logo, support email, social profiles, and structured support or sales contacts—to answer contact or vendor questions.

Instructions

Return Hemmiles' public company and contact information, parsed from the site's Organization JSON-LD: name, website, logo, support email, description, social profiles, and structured contact points (support, sales, etc.).

This is the brief's "get_store_information" for a SaaS vendor.

Args:

locale (optional): which market's page to read (org data is global; default: server locale).
response_format ('markdown'|'json').

Returns JSON: { name, url, logo, email, description, sameAs:[], contactPoints:[{ contactType, email, telephone, url }] }.

Example: "How do I contact Hemmiles?" / "Who makes Hemmiles?".

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
`url`	No
`logo`	No
`name`	No
`email`	No
`sameAs`	No
`description`	No
`contactPoints`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive open-world operation. The description adds valuable context beyond those annotations: the data is public, parsed from Organization JSON-LD, and the organization data is global even when a locale is supplied.

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 the purpose and return shape, then moves through args and examples efficiently. It is appropriately sized, though the line identifying it as the brief's "get_store_information" is internal meta-context that does not help an agent select or invoke the tool.

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?

For a simple read-only tool with no required parameters, full schema coverage, annotations, and an output schema, the description is complete. It covers the source, return shape, locale behavior, and example use cases, leaving no critical gap for correct invocation.

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 both parameters are already well documented in the input schema. The description adds only a small amount of meaning, mainly clarifying that locale selects the market page while the organization data itself is global; otherwise it largely echoes 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 description states a specific verb and resource: return Hemmiles' public company and contact information parsed from Organization JSON-LD, and it enumerates the fields returned. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as hemmiles_get_contact_options, which likely overlaps with the contact-points portion.

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

Usage Guidelines3/5

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

Usage is implied through example questions like "How do I contact Hemmiles?" and "Who makes Hemmiles?", which gives the agent useful triggers. However, it does not state when to prefer this tool over alternatives, especially hemmiles_get_contact_options, nor does it provide exclusions.

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

Deploy Server