Skip to main content
Glama
Sign In
LeadAce

LeadAce

by aitit-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_organizations

List tenant organizations with employee size band, prospect/project counts, and DNC flags. Use for prospecting and filtering by name or domain.

Instructions

List tenant organizations with employee-size band and per-org prospect and project counts; do-not-contact organizations are marked [DNC].

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

Input Schema

NameRequiredDescriptionDefault
qNoSubstring search on name / domain
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.54

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so the description carries the burden. 'List' implies a read-only operationcars, and it discloses output characteristics (employee-size band, counts, DNC marking). However, it doesn't explicitly state side-effect-free behavior or potential performance implications, but for a simple list it's adequate.

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?

One concise sentence that's front-loaded with the action and resource, immediately followed by key output details. No fluff, easily scannable.

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 simple list tool, the description captures the essential return values. It doesn't mention pagination exactly but the schema covers defaults. It doesn't discuss edge cases like empty results or performance, but overall it's adequate for an agent to use correctly.

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

Parameters2/5

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

The description doesn't explain the query parameter q's behavior beyond schema's 'substring' hint. It adds no context for limit/offset, which are self-explanatory. Since schema coverage is only 33%, the description should compensate but doesn't. The user isn't guided on how to filter or paginate effectively.

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?

The description states the exact action ('List') and resource ('organizations'), plus what's included (employee-size band, counts, DNC marking). It clearly distinguishes from other list tools (e.g., list_projects) and conveys the scope (tenant-level).

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?

The description implies when to use (when you need an overview of organizations with counts and DNC status) but doesn't explicitly contrast with alternatives or state exclusions. It's clear enough for an agent to pick this for listing orgs, but doesn't mention not to use it for filtered prospect searches, for example.

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