Skip to main content
Glama

Close Crm

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds behavioral context: events contain source, citation_uri, raw payload; polling is safe; effect of mark_read on future calls. No contradictions.

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?

Description is 4 sentences, front-loaded with main purpose, no filler. Every sentence adds unique information. Efficient and well-organized.

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

Completeness5/5

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

Despite no output schema, description specifies what each event carries (source, citation_uri, payload). Addresses polling, filtering, and alternative access. Complete for a read-only list tool with moderate parameter count.

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 covers all 5 parameters (100%). Description adds context: explains mark_read's effect (flags events read, controls next call), provides filter example (sec_8k), and clarifies ISO timestamp usage. Adds value beyond schema.

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 'Pull fired events from your subscription feed' with specific verb and resource. It distinguishes from sibling tools like list_subscriptions by focusing on event retrieval rather than subscription management.

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?

Provides explicit guidance on filtering (type, since), using mark_read for read tracking, and notes that polling works. Also mentions an alternative HTTP endpoint for scripts/dashboards. Lacks direct comparison to siblings, but no ambiguity exists.

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