Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

job_titles_find

Search and retrieve job titles from Macola 10 business data using title and division filters, pagination, field selection, and count options for targeted lookups.

Instructions

Find Job Titles.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
TitleNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the entire burden of behavioral disclosure, and it discloses nothing. It does not indicate whether results are paginated, how many records come back, whether reads are safe, or what the ten parameters actually control.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two words long, so nothing is wasted, but it is under-specified rather than concise. It is front-loaded but carries no usable content beyond the name.

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?

With 10 parameters, zero schema coverage, no annotations, and no output schema, the definition leaves the agent without nearly all information needed to call the tool correctly. Only the resource name is communicated.

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 10 parameters, and the description adds no meaning for any of them. Terms like 'distinct', 'countOnly', 'totalCount', and 'fields' are left entirely unexplained, which is a serious gap for a tool with this many options.

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 Job Titles" essentially restates the tool name job_titles_find without adding scope, filters, or any distinguishing detail. It gives no basis for choosing it over siblings such as job_titles_get or titles_find.

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, no mention of alternatives, and no exclusions. The verb "Find" weakly implies a search/list operation, but nothing tells the agent when to prefer this over job_titles_get.

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