Skip to main content
Glama

List HVAC articles

list_articles
Read-onlyIdempotent

List AtlantFlow's published HVAC articles, newest first, optionally filtered by topic. Use to browse what guidance exists (AC not cooling, freezing, noises, humidity, heating) before answering a South Florida homeowner's question.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-50).
topicNoOptional topic/category filter, e.g. 'HVAC', 'Maintenance' (case-insensitive substring). Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context beyond that: only published articles are returned and results are ordered newest first. However, it does not describe return format, pagination, or how limit interacts with ordering.

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?

Two tightly written sentences with no wasted material. Scope, ordering, filter behavior, and usage context are all front-loaded and easy to scan.

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?

For a simple read-only list tool with complete parameter descriptions and rich annotations, the description covers what is listed, how it is ordered, and when to use it. It could be slightly more complete by clarifying its relationship to 'search_articles' for targeted queries.

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%, so the schema already documents both parameters including the limit range and topic substring behavior. The description reinforces that topic filtering is optional and mentions example topic areas, but adds no syntax or edge-case guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List AtlantFlow's published HVAC articles.' It adds ordering ('newest first') and optional topic filtering. It does not explicitly distinguish itself from the sibling 'search_articles', so sibling differentiation is only implicit in 'browse' vs. search.

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 gives clear when-to-use guidance: 'Use to browse what guidance exists ... before answering a South Florida homeowner's question.' It does not explicitly say when not to use it or name 'search_articles' as the alternative for targeted 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