Summer

This connector has been deprecated

This was a duplicate manual listing. Use Summer’s official listing, imported from the official MCP Registry. Summer’s MCP server remains active at https://api.gosummer.ai/mcp. Setup and documentation: https://gosummer.ai/docs/mcp-clients.

Check the saved Intercom key against a workspace and preview contact/conversation counts

summer_imports_intercom_preview

Destructive

Check the saved Intercom key against a workspace and preview contact/conversation counts. Save the selected Summer inbox and explicit account-matching choice. Import nothing; send nothing.

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": {
      "company": "<company>",
      "environment": "<environment>",
      "installation": "<installation>",
      "workspace": "<workspace>"
    },
    "name": "summer_imports_intercom_preview"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No		us
`company`	Yes
`workspace`	Yes
`environment`	Yes
`installation`	Yes
`match_accounts`	No
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare non-readonly, destructive, open-world, and non-idempotent behavior. The description adds useful context about what is persisted (selected Summer inbox, account-matching choice) and that no data is imported or sent, which helps clarify side effects. It does not explain what 'destructive' means in this context, whether existing settings can be overwritten, permission requirements, or external calls made under openWorldHint.

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?

Three short sentences, front-loaded with purpose and safety disclaimer, with no wasted filler. The phrase 'explicit account-matching choice' is slightly vague and could be tightened, but overall the structure is efficient.

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

Completeness2/5

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

This is a complex 7-parameter mutation with only 14% schema coverage and no output schema. The description lacks required-parameter explanations, sequencing details, and side-effect specifics needed for an agent to invoke it confidently. It covers the high-level purpose but not enough for correct parameterization.

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

Parameters2/5

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

Schema description coverage is only 14%, so the description must compensate but largely does not. It vaguely references 'workspace' and 'account-matching choice' (likely match_accounts), but company, environment, installation, region, and idempotency_key semantics are left undocumented. 'Selected Summer inbox' is mentioned without mapping to any parameter in the schema.

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?

States specific actions: validate the saved Intercom key against a workspace, preview contact/conversation counts, and persist the selected Summer inbox and account-matching choice. The line 'Import nothing; send nothing' clarifies this is not the actual import execution, distinguishing it conceptually from the import control siblings. However, it does not name the sibling alternatives and the check-plus-save dual nature could be slightly clearer.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance versus summer_imports_intercom_control, summer_imports_intercom_list, or summer_imports_intercom_profiles. It implies a saved Intercom key is a prerequisite but provides no when-not conditions, sequencing, or alternatives.

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

All Summer tools Inspect

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

Need Help?