Skip to main content
Glama

My contacts

my_contacts
Read-onlyIdempotent

The businesses you revealed with their contacts and wa.me links, the last outcome you reported and when the reveal expires (after that the contacts come back masked until revealed again), plus your balance.

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": "my_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful behavior beyond them: reveals expire and contacts revert to masked until revealed again, and the response also surfaces the last reported outcome and the account balance. It still says nothing about ordering, pagination behavior, or whether the balance shown is credits or currency.

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?

A single sentence with no filler, front-loaded with the primary payload (revealed businesses and their contacts). It is somewhat run-on because it enumerates four separate return elements in one breath, but each element earns its place given there is no output schema.

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?

With no output schema, the description does the necessary work of describing the returned contents, including the non-obvious expiry/masking rule. However, it omits how the result set is filtered or paged despite three input parameters, which is a real gap for a list-style tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and it says nothing about the three parameters. The status filter (all/not_contacted/contacted) is the least self-explanatory of these and is completely unmentioned, as are the limit/offset paging bounds.

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 identifies a specific resource — the set of businesses whose contacts the caller has already revealed, plus their wa.me links, last reported outcome, expiry and balance — which is clearly distinct from siblings like reveal_contacts or search_businesses. It lacks an explicit action verb (no 'list'/'get'), so the agent must infer that this is a read of its own revealed-contact ledger rather than a reveal action.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-naming guidance. The phrase 'you revealed' implies the caller should come here to review prior reveals rather than reveal new ones, but that is inference, not stated guidance, and nothing tells the agent how this differs from reveal_contacts or get_business.

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