Skip to main content
Glama

List my businesses

list_businesses
Read-onlyIdempotent

Use this when the user asks which businesses are connected or when their trade licence expires, or first, when another tool needs business_id and the connection may share more than one business. Lists the Fatura Go businesses the user shared with this connection: id, name, base currency, whether the business has a TRN (VAT registered), the user's role, whether it is read-only (closed) and the trade licence issue and expiry dates when the user entered them. Other tools take one of these ids as business_id. Do not use it for clients (list_clients) or for business figures (get_dashboard_summary).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds scope the annotations cannot: results are limited to businesses the user actually shared with this connection, and licence dates appear only when the user entered them. Minor gaps remain around what an empty result means or ordering, but the value-add is real.

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?

Front-loaded with the use condition, then scope, then a field list, then exclusions — a logical order with no filler. The field enumeration is long but each item is returned data an agent can rely on, and the phrase "or first, when another tool needs business_id" reads slightly awkwardly.

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?

No output schema exists, so describing the returned fields is essential, and the description does exactly that while also covering the business_id handoff pattern to other tools. For a zero-parameter read tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add; the description correctly spends no space on inputs. Baseline 4 applies.

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 ("Lists the Fatura Go businesses the user shared with this connection") and enumerates the returned fields (id, name, base currency, TRN status, role, read-only state, licence dates). It explicitly distinguishes itself from list_clients and get_dashboard_summary, so an agent can route without opening any schema.

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?

Gives concrete triggers (user asks which businesses are connected, or about trade licence expiry) plus a sequencing rule: use it first when another tool needs business_id and the connection may share multiple businesses. It also names exclusions with the correct alternatives.

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