Skip to main content
Glama

Tommos

List the companies

list_companies
Read-onlyIdempotent

List the companies of the workspace, as the table on the page Companies shows them: each with its name, its first domain, its status (read from its people, deals and bids, never set by hand), its stage of prospecting, its live people, its open deals, how it came, the sources that found it, and the last touch of any of its people; with the total and how many companies hold each status. Search by the start of a name or a domain; filter by status. With stage, the list is that column of the board «Prospecting» instead, newest moved first, with its count; a column takes no status and no search. Paginate with limit (default 50, max 200) and offset.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 50, max 200)
orderNoBy name (the default), or by the newest touch of the company's people
stageNoA column of the board «Prospecting»: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now), disqualified (Disqualified)
offsetNoRows to skip, for pagination (default 0)
searchNoPart of a name or of a domain
statusNoOne status: customer (Customer), buyer (Buyer), lead (Lead), user (User), past (Past), prospect (Prospect)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / stage / description
      Previous value: -"A column of the board «Prospecting»: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now)"New value: +"A column of the board «Prospecting»: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now), disqualified (Disqualified)"
    • changedInput schema / properties / stage / enum
      Previous value: -[
      -  "found",
      -  "picked",
      -  "people_found",
      -  "outreach",
      -  "replied",
      -  "not_now"
      -]New value: +[
      +  "found",
      +  "picked",
      +  "people_found",
      +  "outreach",
      +  "replied",
      +  "not_now",
      +  "disqualified"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating, and the description wisely doesn't. It does add genuine behavioral context beyond them: status is derived from people, deals and bids and never set by hand, and stage mode changes the result shape to a board column with its own ordering and count. It omits any note on what happens with out-of-range limit/offset or on response envelope details, which keeps it at a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and mode-switching are front-loaded, but the middle is a single sprawling sentence enumerating returned fields, which is dense and hard to scan. The field list does real work given there is no output schema, yet the delivery could be structured into shorter sentences without losing content.

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?

With no output schema, the description carries the return-value burden and does so by naming each column plus the status totals and per-stage count. All six parameters are exercised at least implicitly, and the board-mode behavior is covered. Some phrasing, such as 'how it came', remains vague, and no return-type detail is given for the counts.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns the bump by explaining interactions the schema cannot express: stage overrides status and search, and stage mode reorders by newest move with a count. The remaining params (limit, offset, order, search) are only echoed, with no added format or edge-case detail.

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 companies of the workspace') and anchors it to the Companies table, then enumerates the fields returned. It never explicitly contrasts itself with list_contacts or list_deals, so the sibling distinction is left implicit.

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?

Gives concrete operational rules: search matches the start of a name or domain, status filters, and passing stage switches to the «Prospecting» board column instead. It also states the mutual exclusion ('a column takes no status and no search'), which prevents a real misuse. No alternative tool is named, so it stops short of full routing guidance.

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.