Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

contacts_find

Find Macola contacts by any contact property, such as name, email, account, or division, and control pagination, selected fields, and counts.

Instructions

Get Contacts. Supports filtering by any contact property.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
EmailNo
orderNo
fieldsNo
AccountNo
LastNameNo
distinctNo
divisionNo
pageSizeNo
FirstNameNo
countOnlyNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, but it does not clarify that this is read-only, whether results are paginated, how countOnly/totalCount affect the response, or what permissions are needed. 'Get' weakly implies a read operation, but the behavioral disclosure is minimal for a 13-parameter query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no wasted clauses. However, its brevity reflects under-specification rather than efficient completeness given the tool's 13 parameters and lack of annotations.

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

Completeness2/5

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

For a complex find tool with 13 parameters, zero schema coverage, no annotations, and no output schema, the definition is missing too much: return shape, pagination behavior, response projection, and how count flags work. It establishes only a basic retrieval-plus-filter purpose.

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%, and the description only says filtering works on 'any contact property,' leaving pagination, ordering, projection, distinct, and count parameters undocumented. It gives a small hint about the property-named filters but does not compensate for the 13-parameter schema gap.

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

Purpose3/5

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

The description names the resource ('Contacts') and a retrieval operation ('Get'), and mentions filtering. However, 'Get Contacts' is vague about whether it returns one contact or a list, and it does not distinguish this tool from the sibling contacts_get.

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?

The only usage hint is 'Supports filtering by any contact property,' which implies a filtered lookup but does not say when to use this tool instead of contacts_get or other find tools. There are no explicit exclusions, prerequisites, or guidance on mandatory versus optional filters.

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

Deploy Server

Other Tools