Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_find

Retrieve and filter address records by city, state, postal code, account, or country. Use it to look up business addresses in Macola with paging, field selection, and ordering.

Instructions

Get Addresses. Supports filtering by any address property via query parameters.

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_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
CityNo
pageNo
skipNo
orderNo
fieldsNo
AccountNo
PostCodeNo
distinctNo
divisionNo
pageSizeNo
StateCodeNo
countOnlyNo
totalCountNo
AddressCodeNo
CountryCodeNo

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 supplied, so the description carries the full behavioral burden, yet it discloses almost nothing: not whether this is a read-only operation, what the default page size is, whether results are capped, what the response shape is, or whether ordering matters. Only the existence of filtering is communicated.

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?

Two short sentences, front-loaded and free of filler, so it is structurally clean. The problem is under-specification rather than verbosity — the brevity costs needed information rather than earning space.

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?

For a 15-parameter search tool with zero annotation coverage, no output schema, and no parameter documentation, this description is far from sufficient. An agent knows it can pass field filters but not how to paginate, project fields, request counts, or interpret the response.

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?

Schema description coverage is 0% across 15 parameters. The description says filtering works "by any address property via query parameters" but says nothing about the pagination/control parameters (page, skip, pageSize, order, fields, distinct, countOnly, totalCount), which are the ones an agent will most likely misuse. It adds essentially no semantics beyond the bare property names.

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?

"Get Addresses" states a verb and resource, and the second sentence clarifies that results can be narrowed by any address property. However, a sibling named addresses_get exists and the description never distinguishes listing/filtering from that single-record retrieval, so an agent cannot confidently choose between them from the text alone.

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 versus addresses_get, addresses_address_book, or addresses_create/update/delete. The only guidance is the implied "use query parameters to filter", with no conditions, prerequisites, or exclusions.

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