Skip to main content
Glama

CRM summary

crm_summary
Read-onlyIdempotent

Leads and deals for a client whose CRM is HubSpot, Pipedrive or Zoho CRM (connected on the dashboard): new leads, deals created, won and lost, and the value of won work, over a period. Read-only. For HighLevel, use highlevel_opportunities.

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": {
      "client": "<client>"
    },
    "name": "crm_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoYYYY-MM-DD. Defaults to 30 days ago.
untilNoYYYY-MM-DD. Defaults to today.
clientYesThe client's name, from list_clients

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description's 'Read-only' restates it but does not contradict it. What it genuinely adds beyond the annotations is the prerequisite that the CRM be connected on the dashboard and the scope of aggregation (lead/deal counts plus won value over a period). It does not mention failure modes for unconnected clients or currency handling for the value metric.

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: the first front-loads what is measured and for whom, the second handles scope safety and sibling routing. Every clause carries information an agent needs.

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 does the work of enumerating the returned metrics, which is the key omission most tools leave. It stops short of specifying the shape of the value figure (currency, per-deal vs. aggregate) or whether results are broken down by stage, but it is sufficient for correct invocation.

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?

Schema coverage is 100%, with since/until formats, defaults and the client-name source (list_clients) all documented in the schema. The description adds only the notion of a period, which the schema already implies via since/until. Baseline 3 is appropriate when the schema carries the parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (leads and deals), the supported CRM platforms (HubSpot, Pipedrive, Zoho), and the specific metrics returned (new leads, deals created, won/lost, value of won work) over a period. It explicitly distinguishes itself from the HighLevel sibling, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

It states the routing condition plainly: this tool covers clients on HubSpot, Pipedrive or Zoho, and 'For HighLevel, use highlevel_opportunities.' It also surfaces the prerequisite that the CRM must be connected on the dashboard, which is a real gate on when the call will succeed.

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.