Skip to main content
Glama

OpsRev Roofing AI

List Leap CRM customers

leap_list_customers
Read-only

List or search customers in Leap CRM by keyword, email, or phone number.

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": "leap_list_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
emailNo
limitNo
phoneNo
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish a read-only, non-destructive, open-world operation, and the description consistently portrays a query. Beyond that, it adds little operational detail, leaving unfiltered-request behavior, pagination, and search matching or filter combination unspecified.

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?

A single front-loaded sentence communicates the action, resource, system, and lookup options without filler. Its brevity leaves some informational gaps, but there is no structural problem or unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is sufficient for a basic filtered request, and the annotations supply its safety profile. However, with no output schema or parameter descriptions, it remains incomplete about empty-query behavior, pagination defaults, result shape, and search semantics.

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?

With 0% schema description coverage, the description usefully clarifies that keyword, email, and phone are customer search criteria. It does not explain page or limit, defaults, whether criteria can be combined, or what keyword searches, so its compensation for the undocumented schema is only partial.

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 clearly states the actions, resource, and system: listing or searching customers in Leap CRM. The three lookup methods add useful scope, but the description does not explicitly distinguish the tool from single-customer retrieval or other Leap listing tools.

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?

The wording implies use for browsing customers or finding them when a keyword, email address, or phone number is available. It provides no explicit when/when-not guidance, prerequisites, or routing to an alternative for other lookup needs.

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