Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_get

Retrieve a specific address record by its ID from Macola 10 business data, enabling lookups of customer or location address details.

Instructions

Get the Address for a particular entry by specifying its ID.

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": {
      "id": "<id>"
    },
    "name": "addresses_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAddress ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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. "Get" implies a read, but nothing is said about behavior when the ID does not exist, whether permissions or company scoping apply, or what the response contains — all material for a lookup tool with zero annotation coverage.

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?

One short sentence with no filler, and the key constraint (identify by ID) is front-loaded. It is efficient, though it is arguably too terse for the information an agent needs.

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?

For a one-parameter lookup this is minimally adequate, but with no output schema the description should indicate what an Address record contains or how a missing ID is reported. As written, an agent knows how to call it but not what to expect back.

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 description coverage is 100% and the single id parameter is documented as "Address ID", so the schema already does the work. The description only restates that an ID must be supplied and adds no format, source, or validity detail beyond the schema.

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?

States a specific verb (Get) and resource (the Address) scoped to a single record identified by ID. It is distinguishable from addresses_find or addresses_address_book by the ID-based lookup, though the phrase "a particular entry" is slightly vague about what an entry is.

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?

The phrase "by specifying its ID" implies the precondition that the caller already has an address ID, which is a mild usage signal. It never states when to prefer this over addresses_find or addresses_address_book, and gives no guidance for the case where only a name or partial data is known.

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