Skip to main content
Glama

Close Connector

close_connector
Read-onlyIdempotent

Close CRM sales platform: leads, opportunities (pipeline deals), activities (calls/emails/notes/meetings), full-text search, and organization users (sales reps). Use for sales pipeline reporting, lead/contact lookup, rep-level activity attribution, and sales-funnel analytics. Auth: OAuth 2.0. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesclose_list_leads: List leads in the connected Close CRM organization. Returns lead id, display_name, status_label, contacts, addresses, an | close_get_lead: Get a single Close CRM lead by id, including all custom fields, contacts, addresses, and opportunities | close_list_opportunities: List Close CRM opportunities (pipeline deals): value, status, expected close, lead reference | close_list_activities: List recent activities (calls, emails, notes, meetings) for the Close CRM organization | close_search: Full-text search across Close CRM leads (with embedded contacts and opportunities). Accepts Close Query Language or free | close_list_users: List Close CRM organization users (sales reps) for activity attribution. Returns user id, email, name, and image
paramsNoAction-specific parameters. close_list_leads: {query?: string, limit?: integer, skip?: integer} | close_get_lead: {lead_id: string} | close_list_opportunities: {lead_id?: string, status_type?: string, limit?: integer, skip?: integer} | close_list_activities: {lead_id?: string, user_id?: string, activity_type?: string, limit?: integer, skip?: integer} | close_search: {query: string, limit?: integer} | close_list_users: {limit?: integer, skip?: integer}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: OAuth 2.0 auth, the 15-minute cross-replica provenance_token window, and the attribution-footer/accuracy contract. However, much of this text governs the downstream chart_render tool rather than this connector's own behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a well front-loaded domain summary, but the bulk of the description is boilerplate about chart_render, provenance tokens, footers, and the data-accuracy contract. That material is verbose and largely tangential to invoking this connector, diluting the signal.

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 enum descriptions do the heavy lifting on return fields, and the description covers auth and usage context. It is nearly complete for a read-only connector, though it omits pagination behavior and any explicit note on result limits.

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 description coverage is 100%, with the action enum and per-action param shapes fully documented inline. The description restates the resource categories but adds no syntax, format, or defaulting detail beyond what the schema already provides, so the baseline of 3 applies.

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 names a specific platform (Close CRM) and enumerates the resources it exposes: leads, opportunities, activities, full-text search, and organization users. That is enough for an agent to grasp the domain, but it never states a verb for the tool itself (the actions live only in the enum) and does not distinguish it from the many sibling CRM connectors such as crm_connector or salesforce_connector.

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?

It gives explicit use cases: 'sales pipeline reporting, lead/contact lookup, rep-level activity attribution, and sales-funnel analytics,' which is clear contextual guidance. It offers no exclusions or comparison against alternative connectors, so it stops short of the top tier.

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