Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

One contact in full, with recent touches

connections_contacts_get
Read-only

Use this when the member asks for details about one specific contact - their full info, how they were met, or recent history with that person. Pass the id from connections_contacts_list. Returns every field on the contact record (context, location label, relationship signals, tags, favorite/follow-up flags) plus, by default, their most recent relationship touches (notes, meetings, calls, messages, emails, introductions) from the contact's timeline.

Input Schema

NameRequiredDescriptionDefault
idYesThe contact id from connections_contacts_list.
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).
timeline_limitNoMax touches to include when include_timeline is true (1-100, default 10).
include_timelineNoDefault true: also fetch the contact's recent relationship touches. false skips that second read.

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds real behavioral context beyond that: the full field set returned and that timeline touches come by default, with include_timeline=false skipping a second read — a useful cost/latency hint.

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?

Three sentences, front-loaded with the usage trigger, then the id source, then the return shape. No redundant restatement of the name or title and nothing that does not inform the call.

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?

A read-only single-record tool with full annotation coverage and no output schema; the description lists the returned field groups and the default timeline behavior, which is everything an agent needs to call it and interpret the result.

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%, so the schema already documents id, person, project, timeline_limit and include_timeline, and the description mostly echoes that the id comes from connections_contacts_list. Baseline 3 applies since the schema does the heavy lifting.

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 and resource ('details about one specific contact') plus the scope of what is returned (full record + recent touches). This clearly separates it from list/search-style siblings because it is explicitly single-record and id-driven.

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 an explicit trigger ('Use this when the member asks for details about one specific contact') and a prerequisite ('Pass the `id` from connections_contacts_list'), which routes the agent correctly for discovery-then-fetch. It stops short of excluding near neighbors in the large contacts family (e.g. connections_contacts_recent_interactions or connections_intel_about_person), so a small ambiguity remains.

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