Skip to main content
Glama
veeemlab

@veeemlab/itglue-mcp

by veeemlab

itglue_find_contact_match

Fuzzy-match a contact's first and last name against existing IT Glue contacts. Uses exact email match to force update confidence when available, helping prevent duplicates before creating a new contact.

Instructions

Fuzzy-match a contact (firstName + lastName) against existing IT Glue contacts. If primaryEmail is provided and matches an existing contact's primary email exactly, the score is forced to Update — email is a strong identity signal. Use before creating a new contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNameYesContact first name (required).
lastNameNoContact last name.
organizationIdNofilter[organization_id] to scope the candidate pool.
primaryEmailNoIf provided, exact-match against contact primary email forces Update confidence.
thresholdNoMinimum similarity score to include. Default 0.7.
pageSizeNoCandidates to fetch. Default 100.
Behavior4/5

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

With no annotations, the description explains the fuzzy matching logic, email forcing update, and threshold parameters, but does not detail the output format or whether it can return multiple matches.

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?

Two sentences succinctly cover the tool's purpose and special behavior, with no wasted words.

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?

The description adequately explains the matching logic and parameters. Could mention output format, but not essential for a matching tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. The description adds value by explaining the role of primaryEmail and threshold beyond the schema descriptions.

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 clearly states the tool performs fuzzy matching on firstName and lastName, and specifically mentions the email exact-match behavior, distinguishing it from related search tools.

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

Usage Guidelines4/5

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

Explicitly says 'Use before creating a new contact', providing clear context. Does not mention alternatives, but the purpose is well-defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/veeemlab/itglue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server