Skip to main content
Glama

add_contact_channel

Adds an email address, phone number, or social profile link (LinkedIn, GitHub, Telegram, and more) to a person in a Huly workspace by specifying the provider and value.

Instructions

Add email/phone/… to a person

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "person": "<person>",
      "provider": "<provider>",
      "value": "<value>"
    },
    "name": "add_contact_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
personYesPerson name or id
providerYes
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations only state destructiveHint=false and a title, so the description carries most of the burden and adds nothing behavioral. It does not say whether adding an existing channel duplicates or updates it, what permissions are needed, or what happens on conflicts. For a mutation tool, that is a substantive gap.

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

Conciseness3/5

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

It is a single short phrase with no wasted words and the action is front-loaded, which is good. But the trailing ellipsis reads as unfinished rather than deliberate shorthand, so brevity here edges into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 required parameters, 25% schema coverage, and no output schema, the definition should explain the workspace scoping, provider/value relationship, and success behavior. None of that is present, leaving the agent under-equipped to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 25% – just 'person' is documented. The description's 'email/phone/…' hints that value and provider form a type/payload pair, but it never explains the provider enum, the value format per provider, or what 'workspace' means. It only marginally compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Add' plus 'email/phone/… to a person' conveys the basic action of attaching a contact channel to a person, and it implicitly contrasts with the sibling remove_contact_channel. However, the trailing ellipsis leaves the full scope of what can be added vague, and the description never says 'contact channel' explicitly, so the agent must infer it from the title and provider enum.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as remove_contact_channel or create_person. The agent must decide entirely on its own when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools