Skip to main content
Glama

signvoy_list_contacts

Read-only

Search the workspace address book. This is how you turn a name the user said into the email address a document needs — call it before signvoy_create_document whenever the user names a recipient rather than spelling out their address, instead of guessing an email. The book is shared by everyone in the workspace and fills up automatically from the recipients of every document sent. Archived contacts are excluded. Omit 'q' to browse the whole book.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "signvoy_list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring matched against name and email. Omit to list everything.
limitNoMax results (1–100, default 20).
offsetNoZero-based offset for pagination. Ignored when 'q' is set.
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.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that — the book is workspace-shared, auto-populated from previously sent document recipients, and archived contacts are excluded from results. Those facts materially affect whether an agent can trust a hit or should fall back to asking the user.

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?

Well structured: purpose first, then the routing rule to signvoy_create_document, then behavioral context, then the browse case. The final sentence about omitting 'q' duplicates the schema, so it does not fully earn its place.

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?

There is no output schema, and the description never states what a match returns (presumably name plus email), which the agent needs in order to use results. Everything else an agent needs — safety, data provenance, exclusions, when to call — is present.

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 is 3, and the only parameter guidance in the description ('Omit q to browse the whole book') restates what the schema already says. Nothing is added about how q matches (substring across name and email), pagination, or the workspace_id fallback behavior.

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?

Opens with a concrete verb and resource: 'Search the workspace address book.' It also implicitly distinguishes itself from siblings like signvoy_create_contact and signvoy_create_document by framing itself as the lookup step rather than the write step.

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?

Gives an explicit when: call it before signvoy_create_document when the user names a recipient but not an address. Gives an explicit instead-of: don't guess an email. It also names the browse mode (omit 'q'), so both invocation paths are covered.

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