DirectIQ

directiq_list_contacts

Read-onlyIdempotent

List contacts one page at a time, oldest first, with each contact's ID, email, name, status, tags, and lists. Returns { pageNumber, totalCount, result, hasNextPage }; request the next pageNumber while hasNextPage is true. Use to browse contacts or find an ID. For just the total, use directiq_contact_count instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "directiq_list_contacts"
  }
}

Input Schema

Name	Required	Description	Default
`pageSize`	No	Results per page, 50–500 (default 50)
`pageNumber`	No	1-based page number (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 29, 2026

removedInput schema / properties / page

Removed value: -{
-  "description": "1-based page number",
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / pageNumber

Added value: +{
+  "description": "1-based page number (default 1)",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

changedInput schema / properties / pageSize / description

Previous value: -"Results per page (max 500)"New value: +"Results per page, 50–500 (default 50)"

removedInput schema / properties / pageSize / exclusiveMinimum
```
Removed value: -0
```
addedInput schema / properties / pageSize / minimum
```
Added value: +50
```

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is the ordering guarantee ('oldest first'), the pagination contract (advance pageNumber while hasNextPage), and the response shape. These are real behavioral traits beyond the annotations, though rate-limit or cost details are absent.

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?

Three tight sentences, front-loaded with what it returns and how to paginate, then the alternative-tool routing. No redundant restatement of the name or annotations.

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 no output schema, the description supplies the return shape and page-advancement rule, plus the fallback tool for counting. For a two-parameter read-only list tool this covers everything needed to call it correctly.

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 the baseline is 3, but the description adds meaning beyond the schema by explaining how pageNumber is used in the pagination loop and tying it to hasNextPage. pageSize semantics are left entirely to the schema.

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 ('List contacts'), plus scope details: one page at a time, oldest first, and the fields returned. The final sentence distinguishes it from directiq_contact_count, so an agent can differentiate it from a sibling without inspecting schemas.

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?

Explicitly names the two use cases ('browse contacts or find an ID') and routes the total-only case to directiq_contact_count. That is a concrete when-to-use plus a named alternative, leaving little to inference.

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

All DirectIQ tools Inspect

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.