Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Apps and add-ons - the Chrome add-ons for Connections Email, Connections Schedule and Notes

connections_apps
Read-only

What Connections offers outside this chat: Connections Email, Connections Schedule and Notes each have a Chrome add-on. Returns each add-on's name, browser, status, install_url, a one-line summary and its highlights, plus say, one sentence to hand the member as-is. install_url is null while an add-on is not on the Chrome Web Store (status coming_soon): tell the member it is coming, never invent a store link. Read-only, no side effects.

Input Schema

NameRequiredDescriptionDefault
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/no-destructive annotations it discloses the useful edge case: install_url is null while status is coming_soon, and the agent must never fabricate a store link. It also explains the `say` field is member-facing output to hand over as-is. The closing 'Read-only, no side effects' duplicates the annotations, which costs it a point.

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?

Front-loaded with what is offered, then the return shape, then the null-install_url caveat — a sensible order with no filler sentences. Only the redundant 'Read-only, no side effects' clause fails to earn its place.

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 description does the work of describing the return payload (name, browser, status, install_url, summary, highlights, `say`) and the one null case. That is sufficient for a zero-required-parameter read tool; only the relationship to sibling tooling is unaddressed.

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% and both parameters (`person`, `project`) are documented in the schema with omit-defaults explained. The description adds nothing about them, so the baseline 3 applies — the schema carries the burden entirely.

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?

It names the concrete resource (the Chrome add-ons for Connections Email, Connections Schedule and Notes) and enumerates the fields returned, so an agent knows exactly what this retrieves. It doesn't explicitly contrast with near-neighbours like connections_explore_connectors or connections_mcp_servers, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent infers this answers 'what add-ons exist outside the chat'. It does give one concrete handling rule — pass `say` to the member verbatim and say 'coming soon' when install_url is null — but there is no explicit when-to-use/when-not or named alternative among the many sibling tools.

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

All Connections 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