Skip to main content
Glama

Manage contacts

manage_contacts
Destructive

Add, remove and import the member's contacts (needs an Applystead membership). Actions: add, remove, remove_all, import_csv. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "manage_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
contact_idNoA contact's id from get_contacts list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, so the risk profile is partly covered. The description adds a real prerequisite (Applystead membership) not present in annotations, but says nothing about irreversibility of remove_all, partial failure during import_csv, or rate/format constraints.

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?

Three short sentences, front-loaded with the verb/resource and prerequisite, followed by the action list and the discovery hint. No filler, though repeating the action list that already exists in the schema enum is mild redundancy.

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

Completeness3/5

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

For a destructive, dispatcher-style mutation tool with an open params object and no output schema, the description covers actions, auth prerequisite and field discovery but omits what import_csv expects (CSV shape) and what remove_all wipes. Enough to start an "add", thin for the destructive paths.

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 67%, so the schema already documents action and contact_id. The description's main contribution is the "help" escape hatch for discovering the free-form params object's per-action fields, which is genuinely needed given the untyped nested object, but it never explains any action's actual fields itself.

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

Purpose4/5

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

The description gives specific verbs (add, remove, import) and a clear resource (the member's contacts), and enumerates the action set so an agent knows the operation is a multi-action dispatcher. It implicitly contrasts with the read-only sibling get_contacts, though it never names it.

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

Usage Guidelines3/5

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

It states a prerequisite (needs an Applystead membership) and points to action "help" for per-action fields, which is useful routing. It does not say when to use this versus get_contacts, nor does it warn when each action is appropriate or what remove_all vs remove means in practice.

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.