Skip to main content
Glama

Check a contact lookup

checkContactLookup
Read-onlyIdempotent

Read the result of a lookupContact call, using the lookupId it returned.

Free: checking does not spend another lookup. If status is still "pending", wait about 30 seconds and check once more.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "lookup_id": "<lookup_id>"
    },
    "name": "checkContactLookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
lookup_idYes

Output Schema

NameRequiredDescriptionDefault
emailYes
phoneYes
statusYes
fullNameYes
lookupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, but the description adds genuinely new behavior: checking is free and does not consume another lookup credit, plus the retry cadence for a pending result. It also discloses that inputs and results are recorded for usage tracking and support, which an agent would not otherwise know. It does not cover terminal failure states or expiry of the lookupId.

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?

Front-loaded with the core action, then the free/pending guidance, then the disclosure note. Tight overall; the final privacy sentence is boilerplate but carries real information an agent may need to surface to a user.

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?

With an output schema present, return values need not be explained, and the description covers the workflow position, cost model, and polling cadence. The only shortfall is that the set of possible statuses and their meaning is left to the output schema and the word "pending" alone.

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 only 50%, and the undescribed parameter is exactly the required one — lookup_id. The description compensates by explaining the parameter's provenance ("the lookupId it returned" from lookupContact). orgId is already documented in the schema, so the remaining gap is minor.

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 ("Read the result of a lookupContact call") and explicitly ties itself to the sibling tool that produces the required identifier. An agent can immediately tell this is the follow-up read to lookupContact rather than a fresh search.

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?

Gives clear sequencing guidance: call it after lookupContact, using the lookupId that call returned, and if status is "pending", wait ~30 seconds before checking once more. It stops short of an explicit "do not call before lookupContact" exclusion or advice on what to do if the lookup never resolves, which keeps it from a 5.

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