Skip to main content
Glama
Sign In
HPR Knowledge Base MCP Server

HPR Knowledge Base MCP Server

by macsplit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_host_info

Read-only

Retrieve details about an HPR host, including a list of all their episodes.

Instructions

Get information about an HPR host including all their episodes

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": "get_host_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostIdNoHost ID number
hostNameNoHost name (will search if hostId not provided)
includeEpisodesNoInclude list of all episodes by this host (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and dynamism. The description adds no behavioral traits beyond stating it includes episodes, which is a feature, not a behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 12 words, fully front-loaded. No wasted words; every part contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a tool with no output schema and complex optional parameters, the description lacks details on return format, error handling, or fallback behavior when no parameters are given. Sufficient for simple understanding but incomplete for precise 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% with clear parameter descriptions. The description's phrase 'including all their episodes' slightly reinforces the includeEpisodes parameter but adds no new semantic context beyond the schema.

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?

Description uses specific verb 'Get' with resource 'information about an HPR host including all their episodes', clearly distinguishing from sibling tools like get_episode and search_episodes. No ambiguity.

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?

No explicit when-to-use or when-not-to-use guidance. The description implies usage for host info but doesn't reference sibling tools or provide contextual selection criteria.

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

Deploy Server

Other Tools