Skip to main content
Glama

Pipeline (CRM)

crm_pipeline
Read-onlyIdempotent

Accounts by status and tier with stage probabilities — the weighted where-are-we view. Filter by campaign or see everything.

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

Input Schema

NameRequiredDescriptionDefault
campaign_idNoOnly this campaign. An existing campaign id.

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 read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that this is a weighted, stage-probability view, but it does not clarify computation, return shape, or any other behavioral caveat.

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 short sentences with no filler. The core purpose is front-loaded, and the optional filtering behavior follows immediately.

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 simple read-only aggregate with one optional parameter and no output schema, the description gives a sufficient high-level picture of what is returned: accounts by status and tier with stage probabilities. It could still be slightly more explicit about aggregation details, but nothing essential is missing.

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 coverage is 100%, so campaign_id is already documented. The description adds useful semantic context by stating that filtering by campaign is optional and that omitting it means 'see everything,' which clarifies default behavior beyond the schema.

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 identifies the resource and view: accounts grouped by status and tier, with stage probabilities and a weighted pipeline perspective. It is specific enough to separate this from transactional CRM tools, but it does not explicitly contrast with close siblings such as crm_coverage or crm_campaigns.

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 phrase 'Filter by campaign or see everything' implies how to use the single optional parameter, but it does not say when this tool should be chosen over alternatives. Usage is implied by the 'where-are-we' framing rather than explicitly stated.

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.