Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_address_book

Retrieve addresses and contacts for a specified account to support account lookups and contact management.

Instructions

Get Addresses and Contacts for a given account.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
AccountNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.1/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 disclosure burden, and it discloses almost nothing: no mention of pagination, sorting, result limits, permissions, or whether addresses and contacts are combined or separate. The phrase 'for a given account' hints at scoping but the parameter name is 'Account', so this is thin added value.

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?

It is a single short sentence with no wasted words, but it is under-specified rather than appropriately concise. Nothing is front-loaded beyond the bare purpose because there is nothing else to front-load.

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

Completeness1/5

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

Ten undocumented parameters, no annotations, and no output schema leave the agent with no way to know how to call this tool correctly or what it returns. For this complexity level the description supplies essentially none of the needed context.

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

Parameters1/5

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

All 10 parameters have 0% schema description coverage, and the description explains none of them. Paging/ordering fields (page, skip, pageSize, order, distinct), projection (fields), and the countOnly/totalCount/division flags are completely opaque from both schema and description.

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 a verb ('Get') and two resources ('Addresses and Contacts') scoped to an account, which is more than a tautology. But it doesn't clarify what 'address book' returns versus the sibling tools addresses_find, addresses_get, contacts_find and contacts_get, so an agent cannot distinguish it from those without guessing.

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 statement of when to use this tool rather than addresses_find/addresses_get/contacts_get, nor any prerequisites or exclusions. The only contextual hint is 'for a given account', which is an implicit scoping note, not usage guidance.

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