Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

My contacts

connections_contacts_list
Read-only

Use this when the member asks about their contacts, who they know, their network, people they have met, or who needs following up. Returns the member's own Connections contacts - name, email, phone, company, job title, tags, and whether each needs a follow-up - newest-updated first. Pass query to search by name, email, company, job title or tag; needs_follow_up: true to see only the people waiting on one. Get one contact's full record and recent history with connections_contacts_get {id}.

Input Schema

NameRequiredDescriptionDefault
labelNoOptional: only contacts carrying this tag/folder (a Connections contact folder or label).
limitNoMax contacts to return (1-100, default 25).
queryNoOptional text to search by: matches name, email, phone, company, job title or tag. Words are scored, not required together - a contact matching one word still shows, more matches rank higher.
detailNocompact (default): id, name, email, phone, company, job_title, tags, needs_follow_up. full: every field on the contact record, including relationship signals, favorite/color, location and timestamps.
fieldsNoOptional: return exactly these fields instead of the compact/full set, e.g. ['id','name','phone']. Overrides `detail` when given.
offsetNoContacts to skip, for paging past the first page (default 0).
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
companyNoOptional: only contacts whose company contains this text.
projectNoWorkspace to run this call in (id or name).
needs_follow_upNotrue = only contacts flagged as needing a follow-up. false = only ones that are not. Omit to see both.

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. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, closed-world read. The description adds genuine behavioral context beyond that: result ordering ('newest-updated first') and the exact default field set returned. It doesn't mention paging limits beyond what the schema states or whether totals are returned, so it stops short of a 5.

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

Conciseness5/5

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

Front-loaded with the usage trigger, then the return shape and ordering, then the two most useful parameters, then the sibling handoff. Every sentence carries information and there is no filler.

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?

For a ten-parameter list tool with no output schema, the description covers the return fields and ordering well enough to call it confidently. Minor gaps remain around pagination/total-count behavior and the scoping parameters (person, project), which the schema covers but the description never frames.

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 coverage is 100%, so the schema already documents all ten parameters, including the scored-word query behavior and the compact/full enum. The description restates the query and needs_follow_up usage but adds no syntax or interaction detail beyond the schema, so the baseline 3 applies.

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 concrete verb+resource ('Returns the member's own Connections contacts') and enumerates the returned fields. The trigger phrasing (contacts, who they know, network, people met, follow-up) makes it clearly distinguishable from single-record siblings like connections_contacts_get.

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

Usage Guidelines4/5

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

Gives explicit user-intent triggers and routes the single-record case to connections_contacts_get {id}. It does not, however, distinguish itself from heavily overlapping siblings such as connections_contacts_who_to_follow_up_with, connections_contacts_overdue_followups, or connections_contacts_gone_quiet, even though 'who needs following up' is listed as a trigger.

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