htag-docs

get_guide

Read-onlyIdempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Guide name: 'calling-htag', 'costs' or 'core-concepts'. 'guide://<name>' is also accepted.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the return payload is markdown (not JSON), and the identical content is reachable via guide://<name> resources, which lets an agent avoid a tool call entirely.

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?

One front-loaded sentence opens with the operation and resource, then the guide enumeration, then the resource-alternative note. Dense but every clause carries selection information; the parenthetical contents lists make it slightly run-on but not wasteful.

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?

An output schema exists, so return values need no prose. The description covers the full value set, the priority ordering, the return format, and the equivalent resource path — everything needed to invoke this single-parameter read correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented, so the baseline would be 3. The description goes further by explaining what each accepted value contains (call order/cost rules/paging vs billing units/rates vs place lookup/dates/null handling), which materially helps value selection beyond the schema's bare name list.

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?

States a specific verb ('Return the full markdown') plus the exact resource ('one HtAG agent guide') and enumerates the three valid guide names with their subject matter. This clearly separates it from the sibling list_guides, which enumerates rather than retrieves content.

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?

Gives real guidance by flagging 'calling-htag' as the one to 'read it first,' establishing call order. It also points to the guide://<name> resources as an equivalent access path. It stops short of an explicit when-not-to-use statement or a direct routing rule against list_guides, so it is not quite a 5.

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

All htag-docs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.