Skip to main content
Glama

OpsRev Roofing AI

Get a Leap CRM customer

leap_get_customer
Read-only

Read one customer by ID, including phone numbers, address, and linked jobs.

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": {
      "customerId": "<customerId>"
    },
    "name": "leap_get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile carries itself. The description adds value by naming the returned fields (phone numbers, address, linked jobs), which substitutes for the absent output schema. It does not disclose behavior on a missing or invalid ID, nor how much of the linked jobs is returned.

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 with the retrieval mode first and the returned payload second. Every clause earns its place and there is no filler.

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 one-parameter read tool with annotations covering safety and no output schema, the description supplies both the lookup key semantics and the shape of the response. Only the not-found/error behavior and the depth of "linked jobs" remain unstated, which are minor for this complexity.

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?

With one parameter at 0% schema description coverage, the description clarifies that customerId is a Leap CRM customer identifier used to fetch a single record. The numeric pattern and length bounds come from the schema itself, so nothing important is left unexplained at this parameter count.

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 gives a specific verb and resource ("Read one customer") and adds the key contents (phone numbers, address, linked jobs). The word "one" implicitly separates it from the list-style siblings, but no sibling is named, so differentiation is inferred rather than stated.

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?

Usage is only implied: you call it when you have a customer ID and need the full record. There is no explicit when-to-use versus leap_list_customers, no note about prerequisites such as having an ID in hand, and no guidance on what to do when the ID is unknown.

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