Skip to main content
Glama

Add contact (job hunt)

hunt_add_contact

Add a person. A source is mandatory — how we know them. Never invent a contact (JH-2). The source is the answer to "how do we know this person" — a recruiter who reached out, a referral, a name from an email thread. Effects: contact created.

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": {
      "name": "<name>",
      "source": "<source>"
    },
    "name": "hunt_add_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person.
roleNo
emailNo
notesNo
phoneNo
sourceYesREQUIRED: where this person came from.
companyNoTheir company — created if new.
company_kindNo
linkedin_urlNo
relationshipNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so safety is covered; the description adds genuine policy context beyond that — the 'Effects: contact created' line and the JH-2 rule against inventing contacts, which prevents fabricated data. It omits the side effect that a new company record is created when company is new (visible only in the schema), which keeps this from a 5.

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?

Four short sentences, front-loaded with the action and the mandatory constraint, with no filler. The repeated explanation of 'source' is justified by its required status, though it could be tightened slightly.

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?

No output schema exists, and annotations cover the safety profile, so the essentials are present. Still, for a 10-param creation tool it is silent on duplicate handling, default relationship value, and the company auto-creation side effect — details an agent must infer from the schema or guess.

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 only 30% with 10 parameters, so the burden falls on the description — and it does explain the most important required field (source) in depth, including intent and examples. But the other eight params (role, email, notes, phone, company_kind, linkedin_url, relationship) have empty descriptions and receive no treatment here, leaving most of the surface undocumented.

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?

States a specific verb and resource ('Add a person') scoped to the job-hunt domain via the title, which distinguishes it from hunt_contacts/hunt_get_contact. It does not explicitly contrast itself with the near-identical crm_add_contact or the sibling hunt_check_duplicates, so differentiation relies partly on the title prefix.

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 declares a hard precondition (source is mandatory) and clarifies that source means provenance, with concrete examples (recruiter outreach, referral, email thread). However, it gives no guidance on when to use this versus crm_add_contact, nor on running hunt_check_duplicates first before creating, which the sibling list makes an obvious question.

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.