Skip to main content
Glama

Read company contacts

readCompanyContacts
Read-onlyIdempotent

Read the company's contacts, hiring managers included. list: all contacts with ids, active flag, primary flag. Run this first to find a contact's id. get: one contact by contactId.

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": {
      "command": "<command>"
    },
    "name": "readCompanyContacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
commandYesWhich operation to run: list | get. The tool description explains each.
contactIdNoget/update/delete/set_primary/set_active (required): the contact's id from list

Output Schema

NameRequiredDescriptionDefault
commandYes
contactNo
contactsNo
contactIdNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety needs no restating. The description adds value beyond that in two ways: it discloses the fields returned by list (ids, active flag, primary flag) and states that inputs and results are privately recorded for usage tracking and support, which is real behavioral context the agent would otherwise not have.

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 compact blocks: one line stating the purpose and scope, one line per command mode, and one line of privacy disclosure. The command semantics come before the boilerplate, and there is no redundant phrasing.

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?

This is a read-only tool with rich annotations, a complete input schema and an output schema, so return-format detail is unnecessary. The description covers mode selection, the id-acquisition path and data-handling disclosure. The only omission is which company or organization context applies, which the orgId parameter only partially resolves.

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 gives the meaning of each command enum value (list returns all contacts; get returns one by contactId) and ties contactId to its origin, saying to run list first to obtain it. The schema entry for command even defers to the description, so it carries that weight. The orgId parameter is not discussed, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb plus resource ("Read the company's contacts") and immediately scopes it with "hiring managers included." It also splits the tool into its two modes, list and get, so an agent understands the operation. It does not differentiate itself from adjacent lookup tools such as checkContactLookup, so it stops short of 5.

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?

"Run this first to find a contact's id" is explicit sequencing guidance that tells an agent when list is the prerequisite for get and for id-based siblings. There is no statement about when not to use it or which sibling to prefer for lookups of other kinds, so the guidance is clear but not exhaustive.

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