Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

locations_get

Retrieve Macola location details by ID to view address, inventory, and business data for a specific site. Use it when you need accurate location records for orders, pricing, or inventory lookups.

Instructions

Get the Location information 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": "locations_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/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 disclosure burden. It says nothing about behavior when the ID is unknown, whether the call is read-only (implied by 'Get' but never stated), permissions, or what 'Location information' comprises, leaving a mutation-free but otherwise opaque tool.

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 front-loaded sentence with no filler; it is short without being cryptic. The only cost is that the brevity comes at the expense of the guidance and behavioral detail noted above.

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 with a fully documented schema, the definition is minimally sufficient to invoke the tool. However, with no output schema and no annotations, it omits what the returned location record contains and how a missing ID is handled, which the description could have supplied.

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 'Location ID', so the baseline of 3 applies. The description's phrase 'specifying its ID' restates the schema rather than adding format, source, or validity detail.

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?

States a verb (Get) and a resource (Location information) keyed by ID, so the basic action is clear. But 'a particular entry' is vague — it never says the entry is itself a location rather than some record that has a location — and nothing distinguishes it from the sibling locations_find or inventory_locations_get, so an agent must infer the split from names 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 when-to-use guidance and no mention of alternatives such as locations_find for searching versus fetching by ID. The reader must already know that a known ID is the precondition for this tool.

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