Skip to main content
Glama

HonestCRM

List deals

list_deals
Read-onlyIdempotent

List deals, open by default, with totals for the whole filtered set. Set staleDays to return only deals with no activity for that many days.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Default 1.
limitNoRecords per page. Default 20.
statusNoDeal status. Default open.
stageIdNoOnly deals in this stage.
staleDaysNoOnly deals with no activity (notes, calls, tasks, stage changes) in this many days. A deal that never had activity counts from its creation date.
pipelineIdNoOnly deals in this pipeline.

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 this as a read-only, idempotent, non-destructive, closed-world operation, so the safety bar is low. The description adds genuinely useful behavior beyond them: the default status filter and the fact that totals cover the whole filtered set rather than just the returned page. It says nothing about pagination limits, ordering, or result size, which matter for a six-parameter list tool.

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 sentences, zero filler, with the default-scope fact front-loaded before the one parameter worth calling out. Nothing repeats the tool name or title unnecessarily.

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 filtered list tool with full schema coverage and complete annotations, the description covers what is not otherwise stated: default filtering and the scope of returned totals (substituting for the absent output schema). The remaining gap is pagination/ordering behavior, which the page and limit schema fields partly cover.

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 description coverage is 100%, so the baseline is 3; the description goes slightly beyond by reinforcing the open-status default and summarizing staleDays' intent in one line. The schema still carries the richer detail (which activity types count, creation-date fallback, page/limit defaults), so the description is a helpful summary rather than a substitute.

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?

Names a specific verb and resource ('List deals') and adds two distinguishing traits: an implicit status filter (open by default) and set-level totals. It does not explicitly name a sibling like get_deal or search, so an agent must infer the list-vs-single distinction, but the purpose itself is unambiguous.

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 implied rather than stated: the 'open by default' note tells the agent the default scope, and the staleDays sentence gives the condition under which that parameter should be set. There is no explicit when-to-use guidance versus get_deal for a single record or search for cross-entity queries, and no mention of when to pass status/stageId/pipelineId.

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