Skip to main content
Glama

signvoy_create_contact

Add someone to the workspace address book so they can be found by name later. Rarely needed on its own: sending a document files its recipients automatically, so call this only when the user asks to save a contact ahead of time or wants to record details (company, job title, phone) that a send would not capture. Fails with a conflict if the address is already in the book — call signvoy_list_contacts first if you are unsure.

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": {
      "email": "<email>"
    },
    "name": "signvoy_create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFull name, as it should appear on a document.
emailYesEmail address. The only required field.
notesNo
phoneNo
companyNo
job_titleNo
workspace_idNoTarget workspace UUID. Safe to omit only when the user belongs to exactly one workspace; required otherwise, and omitting it then fails with the list of candidates. Call signvoy_list_workspaces to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the sparse annotations, the description discloses two important behaviors: duplicate email addresses fail with a conflict, and the send flow auto-files recipients. It also gives a concrete pre-check alternative for avoiding that conflict.

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, each earning its place: purpose first, then when to use it, then duplicate-failure handling. There is no repetition or 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 non-destructive create tool with seven parameters and no output schema, this covers purpose, preferred non-use, duplicate handling, and an alternative. The remaining gap is the undocumented notes parameter and no indication of the return value, though no output schema exists.

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?

With only 43% schema description coverage, the description partially compensates by explaining that company, job title, and phone capture details a send would not record. However, it leaves the notes parameter unexplained, and workspace_id is handled only by the schema description.

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?

The description gives a specific verb and resource: 'Add someone to the workspace address book,' which maps directly to creating a contact. It also distinguishes this from sending a document, where recipients are filed automatically.

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

Usage Guidelines5/5

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

It explicitly says this is 'rarely needed on its own' and explains why: sending a document files recipients automatically. It then states the two valid cases for calling it and points to signvoy_list_contacts when unsure.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources