Skip to main content
Glama

list_features

Read-only

List the full HelloBooks marketing feature catalog (145+ items). Filter by category, tier, status, marketedOnly, or substring query.

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_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoFilter by the minimum plan tier / add-on that unlocks the feature.
limitNoMax number of features to return. Default 200.
queryNoOptional substring match against label + shortDescription.
statusNoFilter by rollout status. Defaults to all.
categoryNoFilter to one feature category (core-accounting, invoicing-billing, etc.).
marketedOnlyNoIf true, only return features marketed on the public website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tier / enum
      Previous value: -[
      -  "free",
      -  "pro",
      -  "cpa",
      -  "warehouse-addon",
      -  "manufacturing-addon"
      -]New value: +[
      +  "free",
      +  "pro",
      +  "business",
      +  "cpa",
      +  "warehouse-addon",
      +  "manufacturing-addon"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish this as a safe, closed-world read. The description adds useful context (catalog size of 145+ items) but says nothing about default result volume, pagination via limit, or return shape beyond the count.

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 sentences, zero filler, and the scope statement is front-loaded before the filter list. Every clause maps to something an agent needs.

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 six-optional-parameter read-only listing tool with full schema coverage and annotations, the description covers purpose and scope adequately. The missing piece is routing guidance relative to the overlapping search/category siblings.

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?

With 100% schema description coverage and enums on tier, status, and category, the schema already carries the parameter semantics. The description only restates the filter names already documented in the schema, adding no syntax or interaction detail (e.g., how query combines with category).

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?

States a specific verb and resource ('List the full HelloBooks marketing feature catalog') and quantifies scope at 145+ items, so the agent knows exactly what comes back. It does not distinguish itself from the similar-sounding siblings feature_search or list_feature_categories, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description shows which filters exist, letting an agent infer this is the browse/filter tool. There is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer feature_search for substring lookups 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