Skip to main content
Glama

request_contact

Send a contact request to ONE specific licensee the user has chosen, by license number. This creates the same consent-recorded request a person submits on the profile page; it is not lead routing and we never pick the licensee for the user. Only call after the user has seen the record and explicitly chosen this licensee. Required consent text must be shown to the user verbatim before calling.

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": {
      "state": "<state>",
      "license_number": "<license_number>",
      "first_name": "<first_name>",
      "phone": "<phone>",
      "email": "<email>",
      "zip": "<zip>",
      "project_type": "<project_type>",
      "timeline": "<timeline>",
      "insurance_job": "<insurance_job>",
      "consent_confirmed": "<consent_confirmed>"
    },
    "name": "request_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
emailYes
phoneYes
stateYes
timelineYeswhen needed: emergency, within-month, 1-3-months, just-quotes
first_nameYes
project_typeYesproject type: replacement, repair-leak, storm, inspection, gutters, new-construction, commercial
insurance_jobYesis this an insurance claim: yes, no, not-sure
license_numberYes
consent_confirmedYesUser saw the consent text and agreed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It adds real context (consent-recorded request, parity with the profile-page flow, no licensee auto-selection), but omits downstream behavior – what the licensee receives, permission/auth needs, duplicate handling, rate limits, or failure modes for a write operation.

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 sentences, front-loaded with the action and immediately followed by the scoping and consent constraints. Efficient and free of filler, though it could trim 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?

For a 10-required-parameter mutation tool with no annotations and no output schema, the description covers the essential 'who and when' constraints well but leaves downstream effects, error handling, and most parameter semantics undocumented. Adequate but with clear gaps.

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 40%, so the schema under-documents most fields. The description adds meaning only for license_number and the consent requirement; state, zip, email, phone, first_name, and the enum-like timeline/project_type/insurance_job values get no narrative support, leaving most parameters reliant on self-evident naming.

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?

States a specific verb and resource – 'Send a contact request to ONE specific licensee ... by license number' – and explicitly carves out what it is not ('not lead routing'). This clearly separates it from lookup siblings like search_licensees and check_license.

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 explicit preconditions: 'Only call after the user has seen the record and explicitly chosen this licensee' and 'Required consent text must be shown verbatim before calling.' An agent knows exactly when to invoke it and what must precede the call.

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