Skip to main content
Glama

Get a HeatReady guide

get_heat_guide
Read-onlyIdempotent

Full HeatReady guide by slug (from list_heat_guides) or a 'city industry' phrase: printable checklist, heat-trigger table, local regulatory note, official OSHA/NIOSH sources and the Markdown text. Not legal advice.

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": {
      "slug": "<slug>"
    },
    "name": "get_heat_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGuide slug, e.g. 'phoenix-construction' (a city + industry phrase also works)
include_markdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description earns credit by disclosing the content shape of the response (checklist, trigger table, regulatory note, cited sources) and a scope caveat ('Not legal advice') that no annotation conveys; it omits payload size or pagination behavior.

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?

A single dense sentence front-loads the identifier and input sources before listing contents, with no filler. The enumerated payload list is long but each item is informative, so nothing is obviously wasted.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing the return value and does so by naming the guide's sections. The remaining gap is the include_markdown flag, whose effect is only implied, which matters slightly for a two-parameter tool.

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 coverage is only 50%: slug is documented in the schema, but include_markdown has no description beyond its default of true. The description's mention that the guide includes 'the Markdown text' hints at that flag but never states that include_markdown toggles it, and the dual slug/phrase form it describes is already stated in the schema, so the added meaning is marginal.

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?

The description states a specific retrieval verb and resource ('Full HeatReady guide by slug') and then enumerates exactly what the payload contains: printable checklist, heat-trigger table, local regulatory note, official OSHA/NIOSH sources, and Markdown text. It also names the sibling that produces valid input (list_heat_guides), so it is distinguishable from the list/get siblings without opening a schema.

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?

It clearly tells the agent how to obtain a valid key ('from list_heat_guides') and offers a fallback input form ('city industry' phrase), which is genuine when-to-use context. It stops short of explicit exclusions, e.g. it does not say when to prefer get_outdoor_safety_guidance or get_nws_forecast_and_alerts instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources