Skip to main content
Glama
Meru-Fin-Tech

HelloBooks AI MCP Server

by Meru-Fin-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_articles

Find published articles and blog posts on HelloBooks AI. Filter by country, tag, or free-text query to locate specific comparisons or guides.

Instructions

List published articles on hellobooks.ai — head-to-head compare pages and curated flagship blog posts. Filter by country, tag or free-text query. Use this when a user asks "do you have a blog/article about X?".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoISO country code or "global". Returns articles whose countryRelevance matches OR is "global". Omit to return everything.
tagNoSingle tag to filter on (case-insensitive substring match against the article tag list). e.g. "gst", "1099", "tally".
queryNoFree-text query — substring-matched against the title, excerpt and tags of each article. e.g. "QuickBooks alternative" or "audit trail".
limitNoMax articles to return (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations available. Description does not mention pagination, ordering, return format, or any side effects. Adequate for a read-only list tool but lacks detail.

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 concise sentences: first states purpose, second gives usage context. No wasted words.

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

Completeness3/5

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

No output schema; description does not explain return values or default behavior. Adequate for a list tool with well-described parameters.

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 has 100% description coverage; description only restates filtering capabilities without adding new meaning beyond schema.

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?

Description clearly states 'List published articles on hellobooks.ai' with specific types (head-to-head compare pages, blog posts). Distinct from sibling analysis tools.

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?

Provides explicit use case: 'Use this when a user asks "do you have a blog/article about X?"'. No explicit not-to-use guidance, but siblings are dissimilar.

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

Deploy Server

Other Tools