Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

divisions_find

Retrieve Macola 10 division records with pagination, field selection, ordering, distinct filtering, and optional counts; the division parameter is ignored by the API.

Instructions

Find Division information. Note: the "division" parameter is ignored for this API.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
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 exist, so the description carries the full burden, yet it discloses almost nothing about behavior: no mention of read-only nature, pagination defaults, result shape, or sorting behavior. One genuine disclosure is that the division parameter is ignored, which is useful but far from sufficient for a 9-parameter query tool.

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?

The description is brief and front-loaded with the purpose, then the parameter caveat. It is concise but under-sized relative to the tool's complexity, so brevity here works against clarity rather than for it.

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

Completeness2/5

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

For a 9-parameter finder with no annotations, no output schema, and an ambiguous sibling (divisions_get), the description is far too thin. An agent cannot determine pagination semantics, return contents, or when to prefer this over divisions_get.

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

Parameters2/5

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

Schema description coverage is 0% and nine parameters are undocumented in both schema and description. The description only clarifies one parameter (division is ignored), leaving page, skip, order, fields, distinct, pageSize, countOnly, and totalCount with no semantic explanation anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find Division information" essentially restates the tool name (divisions_find) without adding specifics. It does not say whether this returns a list of divisions or a single division, nor how it differs from the sibling divisions_get.

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 guidance on when to use this tool versus divisions_get or any other division-related call. The only contextual hint is the note that the division parameter is ignored, which is parameter behavior, 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