Skip to main content
Glama

Read contacts

get_contacts
Read-onlyIdempotent

The member's contacts (needs an Applystead membership) and one person's profile. Actions: list, person. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
person_keyNoA person's key from get_contacts or get_outreach.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description contributes the membership prerequisite, which annotations do not carry, but says nothing about pagination, result size, or what happens when the membership is absent.

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?

Two short sentences, front-loaded with the resource and followed by the action list. The parenthetical membership note is slightly awkward but carries real information, so little is wasted.

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

Completeness3/5

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

This is a polymorphic, action-dispatched tool with a free-form nested params object and no output schema, which puts a heavy burden on the description. It covers the actions and defers field detail to the help action, which is reasonable, but an agent still lacks any sense of what list returns or how to shape person lookups.

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 67%, and the description adds a genuinely useful handle for the opaque nested `params` object by pointing to action "help". However, it adds no meaning for the individual actions' fields and does not explain how person_key relates to the person action beyond what the schema pattern and description already say.

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 names the resource (the member's contacts and a single person's profile) and enumerates the read actions (list, person), so an agent knows this is a read tool for contact data. It does not explicitly contrast itself with the sibling manage_contacts, leaving the read-vs-write distinction to be inferred from the title and annotations.

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

Usage Guidelines3/5

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

It states a prerequisite (an Applystead membership) and a discovery path (call action "help"), which gives implied guidance on how to get started. It never says when to pick this over get_outreach or manage_contacts, and gives no conditions under which the tool should not be used.

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.