Skip to main content
Glama

OpsRev Roofing AI

List Leap CRM proposals

leap_list_proposals
Read-only

List proposals in Leap CRM, optionally filtered by job ID, customer ID, status, or keyword.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
jobIdNo
limitNo
statusNo
keywordNo
customerIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/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 is covered. Beyond that, the description adds nothing: no result ordering, no default page size or limit behavior, no statement of what happens when filters match nothing, and no indication of result volume for an open-world read.

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

Conciseness4/5

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

A single front-loaded sentence with no padding or repetition. It is efficient, though its brevity comes at the cost of the pagination and format detail that a six-parameter list tool needs.

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

Completeness2/5

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

For a six-parameter, zero-coverage, no-output-schema list tool, the definition is under-specified. An agent can infer the basic call but not how to page through results, what the default limit is, or how the status filter's 'all' value interacts with the other filters — all gaps the description should have closed.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining six parameters. It names four filters (jobId, customerId, status, keyword) but supplies no semantics for them: status enum values are not mentioned, jobId/customerId are numeric strings per the schema patterns, and page/limit are entirely absent from the description, leaving pagination behavior undocumented.

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 uses a specific verb and resource ('List proposals in Leap CRM') and enumerates the dimensions available for filtering. It is unambiguous, though it does not explicitly contrast itself with any sibling tool; the resource name alone carries the differentiation since no other proposal-listing tool exists in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only lists optional filters, which is parameter restatement rather than usage guidance. It gives no indication of when to prefer this tool over a get-single-proposal or job-level call, no guidance on combining filters, and no note that unfiltered listing may be expensive given openWorldHint.

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