Skip to main content
Glama

Server Details

Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
HtaG-Analytics/htag-mcp
GitHub Stars
0
ChatGPT
–
Claude
HtAG Documentation

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation4/5

Most tools map cleanly to distinct resource types: API endpoints, guides, MCP servers, MCP tools, and micro-agents each have separate list/get operations. There is minor overlap between get_pricing and the 'costs' guide, since both cover billing rates and cost interpretation, which could cause occasional misselection.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: get_* for retrieval and list_* for enumeration. The resource suffixes are predictable and readable throughout.

Tool Count5/5

Eight tools is well-scoped for a documentation/reference server covering endpoints, guides, pricing, MCP discovery, and micro-agents. Each tool appears to earn its place without bloat.

Completeness4/5

The surface covers endpoint discovery/retrieval, guide listing/retrieval, pricing, MCP server/tool discovery, and micro-agent listing. A minor gap is the lack of a get_micro_agent-style tool for inspecting a single micro-agent in detail, though list_micro_agents may provide enough summary information.

Available Tools

8 tools
get_api_endpointA
Read-onlyIdempotent
Inspect

Return the full OpenAPI operation for one HTAG REST endpoint — parameters, requestBody, responses, examples. Use this BEFORE recommending an endpoint so your parameter hints match the live spec. Returns null if the endpoint is not in the catalogue.

Inputs: path (required), method (required). Returns: result

get_guideA
Read-onlyIdempotent
Inspect

Return the full markdown of one HtAG agent guide: 'calling-htag' (call order, cost rules, paging, address keys, property types; read it first), 'costs' (billing units, rates, billing headers) or 'core-concepts' (place lookup, address keys and key spaces, levels, dates, null handling). The same content is served as the guide:// resources.

Inputs: name (required). Returns: result

get_pricingA
Read-onlyIdempotent
Inspect

The HtAG data API rate card: list AUD per unit for each tier (Reference, Standard, Enhanced, Premium, Restricted) and each monthly volume band, linked-plan multipliers, the free allowance and an as-of date, plus how to read the billing receipt on htag tool results. Use it to estimate a call before making it: units x rate x plan multiplier. Also served as pricing://rate-card.

Inputs: no named parameters. Returns: result

list_api_endpointsA
Read-onlyIdempotent
Inspect

List HTAG public REST endpoints. Optional tag (e.g. 'Markets', 'Property', 'Spatial') and query (substring against path / summary) filters. Returns path, method, operationId, tags, and summary for each match.

Inputs: tag, query. Returns: result

list_guidesA
Read-onlyIdempotent
Inspect

List the HtAG agent guides: name, uri, title, summary, updated date and source URL. Read 'calling-htag' with get_guide before planning HtAG data calls.

Inputs: no named parameters. Returns: result

list_mcp_serversA
Read-onlyIdempotent
Inspect

List every MCP server HTAG currently exposes. Each entry includes the server name, a short description, its mount path, and whether it is public (no auth required).

Inputs: no named parameters. Returns: result

list_mcp_toolsA
Read-onlyIdempotent
Inspect

List every tool registered on a named MCP server. Use list_mcp_servers first to discover server names. Each entry includes the tool name, its description, and the JSON-Schema input.

Inputs: server (required). Returns: result

list_micro_agentsA
Read-onlyIdempotent
Inspect

List every callable HTAG micro-agent — turnkey agents that compose endpoint chains and apply HTAG methodology. Examples: 'suburb-analysis', 'suburb-comparison', 'comprehensive-dd'. Useful when a use case is best served by an existing agent rather than raw endpoint composition.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.