Skip to main content
Glama
Sign In

Convocore

by app.convocore.mcp
OverviewDiscussionsAdmin

integrations_read

Read-onlyIdempotent

See every integration of the workspace exactly like the dashboard Integrations page: Google Calendar, Outlook Calendar, Google Sheets, Airtable, Shopify, Calendly, Zoho CRM, Gmail, Outlook mail, Zoho Mail and Google Drive. Start with all_connections (every connection id, account, and which agents use it), then agent_integrations to see and debug what one agent has configured (it lists problems such as a missing calendar, a deleted connection or an inbox whose notifications stopped). resources lists what can be picked for an agent: calendars (google_calendar / outlook_calendar), spreadsheet tabs + header columns (google_sheets, pass sheetId), Airtable bases then tables + fields (pass baseId), Calendly event types, Zoho CRM modules, Shopify store check. A first connection (OAuth login) is always made by the user on the dashboard Integrations page; everything after that is done with integrations_write and integrations_test. Actions: all_connections — every connection of every integration, with the agents using each | agent_integrations — one agent's integrations, settings and detected problems Needs: agentId. | resources — calendars / sheet tabs + headers / Airtable bases, tables, fields / Calendly event types / Zoho modules / Shopify check Needs: type. | calendly_event_types — Calendly event types that can be offered by agents | outlook_connections — connected Outlook accounts | outlook_calendars — calendars of a connected Outlook account Needs: connectionId. | zoho_connections — connected Zoho CRM accounts | zoho_modules — Zoho modules (Leads, Contacts, Deals…) Needs: connectionId. | zoho_fields — fields of a Zoho module Needs: connectionId, moduleApiName. | zoho_agent_config — how an agent syncs with Zoho (lookup and field mapping) Needs: agentId. | zoho_assigned_agents — agents that use Zoho CRM

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "integrations_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
typeNoFor resources: which integration.
forceNoFor zoho_fields: bypass the cache.
orgIdNoOptional organization scope.
typesNoFor all_connections: only these integrations.
actionYes
baseIdNoFor resources type=airtable: base id → its tables and fields.
agentIdNo
sheetIdNoFor resources type=google_sheets: spreadsheet id → its tabs and header row.
connectionIdNoIntegration connection id (from integrations_read all_connections).
sheetTabNameNoFor resources type=google_sheets: tab whose headers to read (default first tab).
moduleApiNameNoFor zoho_fields: Zoho module API name, e.g. "Leads".
headerRowIndexNoFor resources type=google_sheets: header row number (default 1).
includeAgentUsageNoFor all_connections: include which agents use each connection (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the OAuth-on-dashboard prerequisite, the debugging value of agent_integrations (surfacing missing calendars, deleted connections, stopped notifications), and caching via the force param. Strong added value, though return shape is not described.

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

Conciseness4/5

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

Dense but front-loaded: the workflow guidance leads, then a structured action list with 'Needs:' tags. The integration enumeration appears twice (opening sentence and the action list), a minor redundancy, but the length is largely justified by 11 actions and 14 params.

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?

For a polymorphic read tool with no output schema, the description supplies action semantics, required params per action, the OAuth setup prerequisite, and mode defaults. An agent has everything needed to select an action and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 86% schema coverage, the description goes beyond the schema by mapping each of the 11 actions to its required parameters ('Needs: agentId', 'Needs: connectionId, moduleApiName', 'pass baseId', 'pass sheetId'). For a polymorphic 14-param tool this action-to-param mapping is exactly the disambiguation an agent needs.

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?

States a specific verb+resource ('See every integration of the workspace') and grounds it in a familiar analogue ('exactly like the dashboard Integrations page'). It enumerates the concrete integrations covered and clearly positions itself as read (vs. integrations_write/integrations_test), so an agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines5/5

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

It prescribes a sequence ('Start with all_connections, then agent_integrations, resources lists...') and explicitly states the boundary with siblings — first OAuth connection is made on the dashboard, everything after is integrations_write/integrations_test. This is explicit when-to-use, ordering, and alternative routing.

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

All Convocore toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources