Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-14USmethodology registry-public-v1
Searchable tools
120,644
Authless tools
7,742
Auth required
108,393
Described tools
64,965
120,644 tools
- Execute Querypeaka · Execute a saved query by its ID in the Peaka project. Use peaka_list_queries to find available query IDs.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeaka
PluginrequiredData & Analytics - Execute Sql Querypeaka · Runs the given sql query on Peaka.
BEFORE RUNNING THIS TOOL:
1: Use peaka_get_project_metadata to determine which tables should be used in the query and their schemas.
2: Use peaka_list_tables to determine if the tables of interest are cached or not (this response has isCached property)
3: If one or more tables that you need to query are cacheable but not cached:
3a: Warn the user that the results will be limited and ask if you should start the caching process for those tables, and start the caching process using the create cache tool
3b: If the caching is rejected by the user, warn them that the query results will be limited and use LIMIT statements on the query to make sure it doesn't run forever
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Cache Statusespeaka · Get all cache statuses for tables in the Peaka project. Returns the current caching state, execution history, and progress for each cached table.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Connection Detailpeaka · Get connection-specific configuration detail for a data source connection in the Peaka project. The response shape varies by connection type — only the `type` field is guaranteed; remaining fields are connection-specific. Use peaka_list_connections to discover the connectionId.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Materialized Query Statusespeaka · Inspect the auto-refresh state of materialized saved queries in the Peaka project. Returns each query's last refresh status, last/next scheduled execution times, and its schedule settings (interval/cron). Pass a queryId to inspect a single materialized query; omit it to list all of them.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Metadata Refresh Statuspeaka · Check the current status of a metadata refresh job for a specific catalog. Possible statuses: NOT_ACTIVE, COMPLETED, WAITING, ACTIVE, DELAYED, FAILED, PAUSED, STUCK.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Project Metadatapeaka · Get metadata for all catalogs, schemas, and tables in the Peaka project in a single call. Optionally filter by catalogId and/or schemaName. Use this tool to discover the data structure before writing queries.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Querypeaka · Read a single saved query by its ID. Returns the full query object including displayName, inputQuery (SQL), queryType, and the auto-refresh schedule for materialized queries.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Relationspeaka · Get table relationships (foreign keys) for a catalog in the Peaka project. Useful for understanding how tables connect when constructing JOINs — without this, JOIN conditions have to be guessed from column-name similarity. The response is an open-ended object map keyed by relation identifier.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Get Table Statisticspeaka · Get column-level statistics for a table in the Peaka project. Returns the catalog/schema/table identifiers and a per-column distinctFraction (estimated fraction of distinct values vs total rows), useful for cardinality estimation and query optimization.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Catalogspeaka · List all available catalogs in the Peaka project. Returns catalog names, types, and connection info.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Columnspeaka · List all columns for a given table in the Peaka project. Returns column names, data types, and constraints. Use peaka_get_project_metadata first to discover available catalogs, schemas, and tables.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Connectionspeaka · List all data source connections in the Peaka project. Returns each connection's id, name, type, and (for OAuth-based connections) callback URL. Useful for discovering what data sources are wired up; pair with peaka_get_connection_detail for connection-specific configuration.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Projectspeaka · List all projects accessible for the user. Use this tool to discover projectIds, then pass the chosen projectId to subsequent tool calls.PeakaPeakaPluginrequiredData & Analytics
- List Queriespeaka · List all saved queries in the Peaka project. Returns query names, SQL content, and whether they are plain or materialized.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Schemaspeaka · List all available schemas for a given catalog in the Peaka project.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- List Tablespeaka · List all available tables for a given catalog and schema in the Peaka project.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Query Golden Sqlspeaka · Query question/sql pairs from Peaka's golden sql vector store.
If you find an existing query matching the user's question, just use it.
Otherwise use the other tools to figure out the tables and write the query.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Refresh Cache Fullpeaka · Trigger a full refresh on an existing cache in the Peaka project. Use the cacheId returned from peaka_get_cache_statuses.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Refresh Cache Incrementalpeaka · Trigger an incremental update on an existing cache in the Peaka project. Fetches only new/changed rows — much faster than a full refresh. Use the cacheId returned from peaka_get_cache_statuses.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Refresh Materialized Querypeaka · Trigger a refresh on a materialized saved query in the Peaka project. Use the queryId returned from peaka_list_queries for queries whose queryType is "MATERIALIZED".
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Refresh Project Metadatapeaka · Refresh project metadata for a specific catalog. This is a long-running operation that should only be used when a data source has structurally changed (e.g. new tables or columns added). Triggers the refresh asynchronously and returns immediately; it does not wait for completion. Poll peaka_get_metadata_refresh_status to track progress until it reports COMPLETED or FAILED.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Update Cachepeaka · Update cache settings on an existing cache in the Peaka project. This endpoint replaces — not merges — the schedules, so both incrementalSchedule and fullRefreshSchedule must be supplied with the full intended state every call. Each schedule is either {type: "BASIC", expression} with an ISO-8601 duration (e.g. PT6H, P1D, P7D, P30D), or {type: "NONE"} to turn that refresh off. The response reflects the schedule actually applied, which the backend may clamp to its allowed range — check it.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Update Querypeaka · Update an existing saved query in the Peaka project. Adjusts the display name, SQL body, and/or the auto-refresh schedule (for materialized queries). At least one of displayName, inputQuery, or schedule must be provided.
If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.PeakaPeakaPluginrequiredData & Analytics
- Change Quotation Statuschange · Change an Xero quotation's status (e.g. mark as sent, accepted, declined, invoiced, or deleted).Pepper CloudPepper CloudPluginrequiredSales & CRM
- Check Xero Contact Linkcheck · Check whether a CRM account is linked to a Xero contact.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Create Quotationcreate · Create a new Xero quotation for a CRM account. Requires the account to already have a linked Xero contact (xeroContactId). Returns only the new quotation's id — displaying it is handled in the UI.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Accessible Modulesget · Get the list of CRM modules the current user can accessPepper CloudPepper CloudPluginrequiredSales & CRM
- Get Activitiesget · Find activities (notes, tasks, logs, events) linked to a specific business record, latest first.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Associated Recordsget · Get business records associated with (linked to) a given record, grouped by module. Resolve the source record's _id via get_records first.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get CRM Usersget · List all CRM sales and support team members. Not for conversation/message assignees.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Conversation Analysisget · Use this tool to get semantic answers rather than mongodb queries — insights, summaries, sentiment, or trends or details about specific conversations. Use this when the user's question is open-ended or semantic in nature, rather than aimed at a particular module. Call this in parallel with other tools if the request needs it. Call it directly — do not ask the user clarifying questions (channels, date range, status, result count) first; this tool resolves that from the query itself. Not for metadata/counts (use get_conversations_aggregate). Pass the user's query unchanged except for resolving pronouns/references from conversation history. Do not rephrase or summarize the response — return the raw text from the tool to the UI, not a summary or paraphrase.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Conversation Usersget · List users available for conversation assignment. Use user names, not ids, when talking to the user.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Conversations Aggregateget · Run a MongoDB 6.0 aggregation pipeline on conversations and messages — call get_module_schema with moduleId = MSG for rules and schema first, if not already known. You never receive raw field data back — only one of:
Set `queryType` to say which kind of query this is — it changes what you get back:
- "list": use $match / $sort / $skip / $limit to filter and order; the tool returns just the matching conversation ids (an id-only projection, capped at 100). This is a sample — enough to validate the query — NOT the full result set. Do not treat it as complete, and do not tell the user that only a sample exists.
- "analysis": use $group / $count / $sum / $avg and other arithmetic stages to compute counts, totals, averages, and other summaries entirely server-side; the computed result comes back complete — analyze and report it confidently, don't hedge or imply more data exists.
Since no field values come back, do all filtering, sorting, and math inside the pipeline — never expect to read conversations to reason over them afterwards.
The sample cap on ids applies only to this tool call, not to the full result set: when the user wants to see or list conversations, always populate moduleId (MSG) / aggregatePipeline in your response regardless of this cap — that is how the complete result is produced and shown. Never tell the user that only a sample of conversations can be shown, and never propose fetching "the next batch" yourself — that's driven by sortFieldId / sortDirection in your response, not by re-calling this tool.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Conversations Aggregate (Paginated)get · Run a MongoDB aggregation over conversations — use for any conversation list/count/search query. Returns real, complete results — {total, limit, skip, conversationIds} — not a capped sample. Use page/pageSize/sorted to page through results when total exceeds what's already been returned. Call get_module_schema (moduleId: MSG) first for field names and pipeline-building guidance. Don't include $sort/$skip/$limit in the pipeline itself — use page/pageSize/sorted instead.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Current Dateget · Get the current date and time in UTC, as an ISO 8601 string. Call this before building a pipeline for any relative date/time range ("today", "this month", "last 7 days") — never assume or guess today's date.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Exchange Rateget · Get current exchange rates for all supported currencies. Call before summing or averaging amounts across currencies.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Integrationsget · Fetch messaging channel integrations (e.g. WhatsApp, Xero, Telegram) configured for the account.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Module Schemaget · Get the fields, their types, and the record or activityType shape for any CRM modulePepper CloudPepper CloudPluginrequiredSales & CRM
- Get Quotation By IDget · Get one or more Xero quotations' full details by id. Only call this to fetch current data before update_quotation — never for displaying quotation details, which the UI handles.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Quotation Formget · Get Xero form configuration (items, tax rates, branding themes, currencies) needed to build a quotation.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Quotations Aggregate (Paginated)get · Run a MongoDB aggregation over quotations — use for any quotation list/count/search/analysis query. Returns real, complete results — {recordsTotal, limit, skip, quotations} — not a capped sample. Use page/pageSize/sorted to page through results when total exceeds what's already been returned. Call get_module_schema (moduleId: "QTM") first for field names, ObjectId rules, and pipeline-building guidance. Don't include $sort/$skip/$limit in the pipeline itself — use page/pageSize/sorted instead.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Records (Paginated)get · Query a CRM module's records, or Activities (NOTE, TASK, LOG, EVENT) when activityType is given, with a MongoDB aggregation pipeline. Returns real, complete results — {total, limit, skip, records} — not a capped sample. Use page/pageSize/sorted to page through more when total exceeds what's already been returned. Build the pipeline from the field ids and types from get_module_schema. Always project raw database paths only (e.g. records.F2: 1, records.F3: 1).Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Suggestion Paramsget · Get valid assignee suggestions for a CRM module — call before assigning a record to find who can be assigned. If same name appears, take confirmation from user before assigning. Do not call this when asked to assign to "me"Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Ticket Infoget · Fetch comments, checklist, and/or timeline for a ticket.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Tickets Aggregate (Paginated)get · Run a MongoDB aggregation over tickets — use for any ticket list/count/search/analysis query. Returns real, complete ticket documents — {total, limit, skip, records} — not a capped sample or id-only list. Use page/pageSize to page through results when total exceeds what's already been returned. Call get_module_schema (moduleId: "TM") first for field names, ObjectId rules, and pipeline-building guidance. Don't include $skip/$limit in the pipeline itself — use page/pageSize instead; $sort is fine to include in the pipeline.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Get Xero Contactsget · List Xero contacts available for linking to a CRM account.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Save Activitysave · Create a new activity (mode='create', NOTE/TASK/LOG/EVENT) linked to one or more business records, or update fields on an existing one (mode='update'). For updates, include only the fields being changed, using exact fieldIds. Before creating, collect the required fieldsfrom the user — never invent, assume, or auto-fill values the user didn't provide. Use defaults unless the user explicitly overrides them.Pepper CloudPepper CloudPluginrequiredSales & CRM
- Save Business Recordsave · Create a new business record (mode='create') or update fields on an existing one (mode='update').
For updates, include only the fields being changed.
Field value formats:
- Text: String value directly
- Number: Numeric value
- Date/DateTime: ISO 8601 format
- Currency: {"currencyType": "USD", "amount": 1000}
- Phone: String with country code
- Email: Valid email string
- Reference fields (Account, Assigned to): Use the ID
- Enum/Select: Use raw enum value (e.g. "OPEN", not display label)
- Percent: string (e.g. "75")Pepper CloudPepper CloudPluginrequiredSales & CRM
- Save Ticketsave · Create a new support ticket (mode='create') or update fields on an existing one (mode='update'), including escalating it or closing it.
Call get_module_schema (moduleId: "TM") first for valid pipeline/pipelineStage IDs and confirm details with the user before creating.
For updates, records must contain ONLY the fields actually changing — omit anything unchanged, and never pass null for a field just to keep it as-is. Escalate with escalate=true, or close via records.status="CLOSED".Pepper CloudPepper CloudPluginrequiredSales & CRM
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.