Skip to main content
Glama

list_accountants

Read-only

Search every published HelloBooks accountant profile with all public details, contacts, services, credentials and availability. No availability filter is applied by default. Follow nextPage until null to retrieve all matches. Source status distinguishes live, stale and unavailable data.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
pageNo
queryNoSearch firm, principal, biography, location, specialties, industries, credentials or language.
countryNoDirectory country slug, e.g. united-states, india. Omit for all countries.
pageSizeNoDefault 25. Follow nextPage until null to retrieve every matching full profile.
specialtyNo
acceptingClientsNoOmit to include every published firm, including those not accepting new clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: default unfiltered availability, the mandatory pagination loop ('Follow nextPage until null'), and the meaning of source status (live, stale, unavailable) — the last being important because it tells the agent results may be outdated. It does not mention result ordering or an approximate result volume, which keeps it short of a 5.

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?

Four short sentences, each carrying distinct information (scope, default filtering, pagination, data-quality semantics), with the scope front-loaded. No filler or restated name/title, though the pagination instruction is duplicated in the pageSize schema description.

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 7-parameter read-only listing tool with no output schema, the description covers the essentials an agent needs to call it correctly and iterate pagination, plus a caution about stale source data. It omits the return envelope shape and default page size, but those are either schema-documented or safely discoverable from the first response.

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 57%, so several parameters (city, page, specialty) carry no documented meaning in either place. The description partly compensates by explaining the default availability behavior that maps to acceptingClients, but it adds nothing about city vs country, specialty vs query, or page semantics beyond what the schema already says. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Search every published HelloBooks accountant profile,' and enumerates what comes back (contacts, services, credentials, availability). It does not explicitly contrast with the sibling get_accountant, so an agent must infer that this is the bulk-search path versus the single-record fetch, but the scope ('every published profile') is clear enough to differentiate in practice.

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 implied rather than stated: the agent learns this tool is for broad directory search and that it should page through results, and 'No availability filter is applied by default' signals the default breadth. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. use get_accountant for a single profile), so the routing decision is left to inference.

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