hp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_newsA | Fetch the news (お知らせ) list from the HP. Returns news items, total count and categories. |
| get_news_detailA | Fetch a single news article by its number, including previous/next links. |
| get_companyB | Fetch the company (会社情報) profile from the HP. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools target clearly distinct purposes: news listing, news detail, and company profile. get_news and get_news_detail are related but well-differentiated by list vs. single-article granularity. The main potential confusion is an agent confusing get_news's list vs. detail, but the descriptions make the distinction clear.
All tools follow a consistent get_<noun> pattern with snake_case, which is predictable and readable. The only minor deviation is the mixed use of get_news (list) vs. get_news_detail (single), which slightly breaks the implied noun granularity, but overall the convention is uniform.
Three tools is on the low end but borderline acceptable for a simple company HP content server. The scope appears to be news + company info, which a 3-tool set could plausibly cover, though it feels thin for a full website.
The news lifecycle (list + detail) and company profile are covered with no dead ends for the demonstrated use case. However, there are notable gaps: no pagination/create/update/delete for news, no other HP sections (e.g., product listings, contact info), and reading is the only supported operation. For a read-only company wiki this is acceptable, but it lacks breadth.