Skip to main content
Glama

Close Crm

by io.github.pipeworx-io

Close List Activities

close_list_activities
Read-onlyIdempotent

List activities for a lead — calls, emails, notes, SMS, meetings, and status changes. Returns a data array (with id, _type, type, date_created, and type-specific fields) plus has_more / total_results. Requires lead_id. Page with _limit / _skip to walk a lead's timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_skipNoNumber of results to skip for pagination (default 0)
_limitNoResults per page (default 100, max 200)
_apiKeyYesClose API key
lead_idYesLead ID whose activity timeline to fetch

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnly, openWorld, idempotent, non-destructive. The description adds response structure details (data array with fields, has_more, total_results) and pagination behavior, complementing annotations without contradiction.

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?

Three sentences, front-loaded with main purpose, no redundant text. Efficiently conveys key information.

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?

Covers required parameters, pagination, and response fields. Lacks output schema but description compensates with field listing. Could mention _apiKey but schema covers it.

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 covers 100% of parameters with descriptions. The description reinforces lead_id and pagination usage but does not add significant new semantic detail beyond what the schema provides.

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 clearly states 'List activities for a lead' with specific types (calls, emails, notes, SMS, meetings, status changes). It distinguishes from sibling tools like close_list_contacts and close_list_opportunities by targeting lead activity timelines.

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

Usage Guidelines4/5

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

The description specifies required lead_id and pagination with _limit/_skip, giving clear usage context. It lacks explicit when-not-to-use or alternative tools, but the sibling list implies differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Close Crm toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Multiple Pipeworx tools overlap significantly (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, entity_profile, compare_entities, recent_changes all query similar data). Close CRM tools are distinct but the overall set mixes two domains, causing confusion.

Naming Consistency2/5

Tool names mix snakes (close_get_lead), lowercase (ask_pipeworx), and descriptive phrases (scan_competitor_ai_presence). No consistent verb_noun pattern across the entire set.

Tool Count2/5

37 tools is excessive for a focused server. The combination of Close CRM and Pipeworx data services creates scope creep; many tools could be separate servers.

Completeness3/5

Pipeworx tools offer extensive data coverage, but Close CRM lacks update/delete operations for leads, contacts, and opportunities, leaving basic CRUD gaps.

Resources