Skip to main content
Glama

CRM clients

dosai_list_contacts
Read-onlyIdempotent

Clients of the CRM project (one person = one card across WhatsApp, Telegram and Instagram), freshest first; search by name or phone. scope=personal for the owner's personal contacts. Next page: before from the last row.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "dosai_list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
scopeNo
beforeNo
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changed
    • removedInput schema / properties / workspace_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered elsewhere. The description still adds real behavior: default sort order (freshest first), cross-channel person merging, and cursor pagination via `before` taken from the last row. It stops short of describing result caps or what a card contains, so a 4 is not fully earned.

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 dense, front-loaded sentences with zero filler; identity-merge semantics come first, then search and pagination. Every clause carries information an agent needs to call the tool correctly.

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 supplies the essential return-shape cues (one card per person across channels, freshest-first ordering) and covers pagination, which is the main failure mode for a list tool. Minor gaps remain, such as page size or whether filtered searches preserve the same ordering, but nothing blocking 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?

Schema coverage is only 25%, so the description must compensate, and it largely does: `q` is clarified as name or phone search, `scope` gains concrete meaning (personal vs the project's clients), and `before` is explained as the next-page cursor taken from the last row. Only `workspace_id` is left to the schema, where it is already documented.

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+resource: listing the CRM project's clients, with the useful disambiguation that one person = one card across WhatsApp, Telegram and Instagram, plus ordering ('freshest first'). It does not explicitly distinguish itself from nearby siblings such as dosai_list_leads or dosai_list_deals, so an agent must still infer the client-vs-lead boundary.

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?

Implies usage through 'scope=personal for the owner's personal contacts' and 'search by name or phone', giving the agent the two main entry modes. There is no explicit when-to-use/when-not statement and no named alternative for lead or deal lookups, leaving the routing decision implicit.

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