Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Find which contact someone is

connections_contacts_resolve_contact
Read-only

Work out which ONE of this member's own contacts a name, email or company means, before acting on that person. outcome is 'resolved' (one exact match, in contact), 'ambiguous' (several, in candidates), 'confirm' (only a partial or near spelling matched: ask the member) or 'none'. matchedOn says what matched. If scanComplete is false, 'none' means not found among the contacts read. Read-only.

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name, email or company exactly as the member said it.
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

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description defines the four outcome values, says what `matchedOn` and `contact`/`candidates` hold, and flags the critical caveat that a 'none' result is only conclusive when `scanComplete` is true. That is genuine behavioral context an agent could not infer from annotations.

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 action and its scope, then the outcome vocabulary in a compact enumeration. Dense but every clause carries information; the trailing 'Read-only.' is the one redundant sentence given readOnlyHint=true.

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, and the description covers the return contract (outcome values, contact, candidates, matchedOn, scanComplete) as well as the pre-action purpose. An agent has everything needed 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 coverage is 100%, so the baseline applies; each parameter is already documented in the schema. The description reinforces that the `name` value can be a person, email or company, but adds no format or matching-rule detail beyond that.

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 object ('work out which ONE of this member's own contacts a name, email or company means') and scopes it to the member's own contacts. This clearly separates it from lookup siblings such as connections_contacts_get or connections_contacts_find_warm_path.

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?

'before acting on that person' gives an explicit trigger point, and the 'confirm' outcome tells the agent to go back to the member rather than proceed. No sibling is named as an alternative, so it stops short of full routing guidance.

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