Skip to main content
Glama
Sign In

DirectIQ

by com.directiq.mcp
OverviewDiscussionsAdmin

directiq_get_contact

Read-onlyIdempotent

Get one contact by numeric ID: email, first and last name, status, created and updated dates, tags, lists, and notes. Use when you already have the ID; to find a contact, page through directiq_list_contacts. Returns an error if no contact has that ID.

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": {
      "id": "<id>"
    },
    "name": "directiq_get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric contact ID (from directiq_list_contacts or directiq_get_contact)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Numeric contact ID"New value: +"Numeric contact ID (from directiq_list_contacts or directiq_get_contact)"
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already say readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the not-found behavior ('Returns an error if no contact has that ID') and enumerates the returned fields, which is real context beyond the annotations. It still does not describe output shape or format in detail, so it falls short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns and then with how it relates to the sibling; there is no filler. Every clause, including the error behavior, carries information an agent needs.

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

Completeness5/5

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

With one documented parameter, a full annotation set, and no output schema, the description carries the return-value burden itself and does so by listing the fields. Nothing essential for a correct call is missing.

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%: the schema defines the single id parameter and says where to take its value, and the description reiterates that the ID is numeric. Up to the baseline, the description adds no syntax or edge-case detail beyond what the schema already provides.

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?

It names a specific verb and resource ('Get one contact by numeric ID'), lists the fields the call returns, and explicitly contrasts itself with directiq_list_contacts. Without opening either schema, an agent can distinguish it from its closest sibling.

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?

The description states the condition for using this tool ('when you already have the ID') and the alternative for the opposite case ('to find a contact, page through directiq_list_contacts'). It covers both when to use the tool and when not to use it.

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

All DirectIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources