Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

divisions_get

Retrieves a single Macola division's details by division code, so you can verify division information before using it in orders, pricing, or other business records.

Instructions

Get one Division's information, given the Division Code.

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

Input Schema

NameRequiredDescriptionDefault
idYesDivision code

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 burden of behavioral disclosure. 'Get' implicitly signals a read-only, non-destructive operation, but nothing is said about failure behavior for an unknown code, permission requirements, or what 'information' actually contains.

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 sentence, front-loaded with the verb and resource, with no filler. The only weak word is the vague noun 'information', which could have been made more concrete.

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?

This is a simple one-parameter read operation, so little explanation is required. However, with no output schema, the description's vague promise of 'Division's information' leaves the agent without any sense of the returned shape, which is the one real gap.

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 coverage is 100% and the single parameter is already documented as 'Division code'. The description repeats the same concept ('Division Code') without adding format, length, or example values, so a baseline 3 is appropriate.

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), resource (Division), and cardinality ('one'), which separates it from list-style siblings such as divisions_find. It stops short of naming the sibling alternative, but the single-record scope is unmistakable.

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 'given the Division Code' implies the caller must already know the identifier, which is usable context for when to call it. There is no explicit when-not guidance or named alternative for lookup-by-name or listing, so usage is only implied.

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