Skip to main content
Glama

Read an HVAC article

get_article
Read-onlyIdempotent

Read the full text of one AtlantFlow article (troubleshooting steps, causes, typical South Florida advice) by URL or id. Use after search_articles or list_articles, to answer a homeowner's how-to or why-is-my-AC-doing-X question. Includes the publication date, the license line and a call-to-action. Article costs are general ranges, not a quote.

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": {
      "url_or_id": "<url_or_id>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_or_idYesArticle URL (as returned by search_articles / list_articles) or numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered; the description adds real value by disclosing what the payload contains (publication date, license line, call-to-action) and the important caveat that article costs are general ranges, not a quote. It falls short of 5 because it says nothing about behavior on an invalid or stale URL/id (error vs. empty result).

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?

Three tight sentences, front-loaded with the operation and followed by usage and content expectations. Every clause carries information an agent can act on, with no filler or restatement of the title.

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?

For a one-parameter, read-only lookup with full annotation coverage and no output schema, the description supplies everything an agent needs: what it returns (steps, causes, advice, date, license, CTA), when to reach for it, and a caveat on how to interpret pricing content.

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 100% for the single parameter, and the schema itself already explains that the URL comes from search_articles/list_articles or that a numeric id is accepted. The description's 'by URL or id' restates rather than extends the schema, so the baseline 3 applies; no format, normalization, or precedence rules (e.g., URL takes priority over id) are added.

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 and resource ('Read the full text of one AtlantFlow article') plus the concrete content classes it contains (troubleshooting steps, causes, regional advice). The identifier options ('by URL or id') and the framing against list_articles/search_articles make it unmistakable which sibling it complements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it 'after search_articles or list_articles' for homeowner how-to and 'why-is-my-AC-doing-X' questions, naming the prerequisite alternatives and the intent that selects this tool over them. No warranted when-not guidance is missing for a read-only lookup.

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