Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Save a new contact

connections_contacts_save_contact

Save ONE new person to this member's own contacts, with only the details the member gave (name is required; company, title, email, phone and the like are optional). Call this when the member asks to add or remember someone. It looks up nothing.

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's full name, as the member said it.
emailNoOnly if the member gave one; never guess.
phoneNoOnly if the member gave one; never guess.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
companyNoEmployer, if mentioned.
contextNoOne or two sentences on who they are and why to remember them; becomes the contact's note.
dry_runNoPreview only.
projectNoWorkspace to run this call in (id or name).
jobTitleNoRole or title, if mentioned.
lastMetLabelNoHow or where they met, in a few words. Omit if not said.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Employer, if mentioned. Omit when unknown."New value: +"Employer, if mentioned."
    • changedInput schema / properties / context / description
      Previous value: -"One or two sentences on who they are and why the member wants to remember them, in the member's own framing. This becomes the note on the contact."New value: +"One or two sentences on who they are and why to remember them; becomes the contact's note."
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only; nothing is written."New value: +"Preview only."
    • changedInput schema / properties / email / description
      Previous value: -"Email address, only if the member actually gave one. Omit otherwise - never guess."New value: +"Only if the member gave one; never guess."
    • changedInput schema / properties / jobTitle / description
      Previous value: -"Role or title, if mentioned. Omit when unknown."New value: +"Role or title, if mentioned."
    • changedInput schema / properties / lastMetLabel / description
      Previous value: -"How or where they met, in a few words ('Coffee at the Northwind offsite'). Omit when the member did not say."New value: +"How or where they met, in a few words. Omit if not said."
    • changedInput schema / properties / phone / description
      Previous value: -"Phone number, only if the member actually gave one. Omit otherwise - never guess."New value: +"Only if the member gave one; never guess."
  2. Changed2 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: return what this call would do, with nothing written."New value: +"Preview only; nothing is written."
    • 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. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds real value by saying only member-supplied details are stored and that no lookup/enrichment happens, but it omits what the call returns, whether duplicates are created, and what the dry_run preview yields.

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?

Two short sentences, front-loaded with the scope constraint, with no filler. The 'It looks up nothing' closer is a compact and high-value qualifier.

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 10-parameter but largely optional create operation with no output schema, the description covers the essentials: what is written, what is required, and that no resolution occurs. A note on duplicate handling or the returned contact would close the remaining gap.

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 goes slightly beyond by marking name as the sole required field and framing all other attributes as optional and member-supplied only. It does not explain the scoping parameters (person, project) or dry_run, which remain schema-only.

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 ('Save'), resource ('ONE new person') and scope ('to this member's own contacts'), plus which fields are required vs optional. This clearly separates it from siblings like connections_contacts_import_contacts, connections_contacts_resolve_contact, and connections_contacts_update_role.

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 ('when the member asks to add or remember someone') and a useful exclusion ('It looks up nothing'), which tells the agent not to expect resolution or enrichment. It stops short of naming the alternative tools to use for lookup/dedupe, so it is clear but not fully routing.

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