Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

How do I... - find the right Connections tool for a task

connections_help
Read-only

Use this BEFORE guessing which Connections tool to call, or when unsure what Connections can do at all. Pass intent in the member's own words ('create an event', 'my todos', 'post a deal', 'remember this', 'who do i know') and get back the ONE tool to call: its required fields, optional fields, a runnable example, and whether it needs confirmation before calling. Add domain to disambiguate when the intent alone could mean more than one thing. With no intent, or one that matches nothing, returns the full capability map instead: every domain Connections covers, its canonical read tool and write tool, one line each - the answer to 'what can you do'.

Input Schema

NameRequiredDescriptionDefault
qNoAlias for `intent`.
queryNoAlias for `intent`.
domainNoOptional: narrow matching to one domain when intent alone is ambiguous (e.g. 'add' could be a todo or a contact).
intentNoWhat the member wants to do, in plain words (e.g. 'create an event', 'my todos', 'remember this'). Omit for the full capability map. `question`, `query` and `q` are accepted aliases; any OTHER argument name is reported back in `ignored_params` rather than silently dropped.
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).
questionNoAlias for `intent` - this tool's title invites it, so it is accepted rather than discarded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "contacts",
-  "todos",
-  "calendar",
-  "events",
-  "deals",
-  "email",
-  "notes",
-  "memory",
-  "workspace",
-  "introductions",
-  "receipts",
-  "connectors",
-  "pages"
-]New value: +[
+  "contacts",
+  "todos",
+  "calendar",
+  "events",
+  "deals",
+  "email",
+  "inbox",
+  "notes",
+  "memory",
+  "workspace",
+  "introductions",
+  "receipts",
+  "connectors",
+  "pages"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "contacts",
-  "todos",
-  "calendar",
-  "events",
-  "deals",
-  "email",
-  "notes",
-  "memory",
-  "workspace",
-  "introductions",
-  "receipts",
-  "connectors"
-]New value: +[
+  "contacts",
+  "todos",
+  "calendar",
+  "events",
+  "deals",
+  "email",
+  "notes",
+  "memory",
+  "workspace",
+  "introductions",
+  "receipts",
+  "connectors",
+  "pages"
+]
    • 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "contacts",
-  "todos",
-  "calendar",
-  "events",
-  "deals",
-  "email",
-  "notes",
-  "memory",
-  "workspace"
-]New value: +[
+  "contacts",
+  "todos",
+  "calendar",
+  "events",
+  "deals",
+  "email",
+  "notes",
+  "memory",
+  "workspace",
+  "introductions",
+  "receipts",
+  "connectors"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "contacts",
-  "todos",
-  "events",
-  "deals",
-  "email",
-  "notes",
-  "memory",
-  "workspace"
-]New value: +[
+  "contacts",
+  "todos",
+  "calendar",
+  "events",
+  "deals",
+  "email",
+  "notes",
+  "memory",
+  "workspace"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "contacts",
-  "todos",
-  "events",
-  "deals",
-  "notes",
-  "memory",
-  "workspace"
-]New value: +[
+  "contacts",
+  "todos",
+  "events",
+  "deals",
+  "email",
+  "notes",
+  "memory",
+  "workspace"
+]
  7. Changed5 schema fields changed
    • changedInput schema / properties / intent / description
      Previous value: -"What the member wants to do, in plain words (e.g. 'create an event', 'my todos', 'remember this'). Omit for the full capability map."New value: +"What the member wants to do, in plain words (e.g. 'create an event', 'my todos', 'remember this'). Omit for the full capability map. `question`, `query` and `q` are accepted aliases; any OTHER argument name is reported back in `ignored_params` rather than silently dropped."
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for `intent`.",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Alias for `intent`.",
+  "type": "string"
+}
    • addedInput schema / properties / question
      Added value: +{
+  "description": "Alias for `intent` - this tool's title invites it, so it is accepted rather than discarded.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[]
  8. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already establish safe read-only, non-destructive, closed-world behavior. The description adds useful context about what comes back (required fields, optional fields, a runnable example, confirmation requirement) and the fallback to a full capability map. It does not, however, discuss matching strictness beyond 'matches nothing', confidence signals, or how ambiguous multiple matches are resolved beyond the `domain` nudge.

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 the trigger condition, then the invocation pattern, then the fallback behavior. Dense but nearly every clause carries operational meaning; the parenthetical example list of intents is slightly long but illustrative.

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?

There is no output schema, so the description carries the return-value burden and does so fully: it names what the response contains when a match is found and what it contains when it is not. For a router tool with 7 optional params, this is complete enough to use correctly without probing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still earns above baseline by explaining intent should be phrased in the member's own words with concrete examples, and by explaining the purpose of `domain` (disambiguating when intent alone is ambiguous, like 'add').

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?

The description states a specific verb and resource: it resolves an intent into the one Connections tool to call, returning that tool's fields, example, and confirmation requirement. It clearly distinguishes itself from the ~90 sibling tools, which are the very tools it routes to.

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 says explicitly when to use it ('BEFORE guessing which Connections tool to call, or when unsure what Connections can do at all') and names the disambiguation mechanism via `domain`. It also covers the no-match/browse case, so an agent knows the fallback path without experimenting.

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