Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

titles_find

Find salutation lookup values such as Mr., Mrs., or Dr. for customer records, with paging, field selection, and count options.

Instructions

Find Titles (salutation lookup values, e.g. Mr., Mrs., Dr.).

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": "titles_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.6/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 and delivers almost nothing: it does not say whether this is a read-only lookup, whether results are paginated, how large the default page is, or what the response shape looks like. For a nine-parameter query tool with zero annotation coverage, this is a substantial gap.

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 tight sentence with the disambiguating detail front-loaded and no wasted wording. It is concise, though the brevity is partly a symptom of under-specification rather than disciplined editing.

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?

Given nine optional parameters, no annotations, and no output schema, the definition is far too thin for an agent to invoke it confidently. It does not explain pagination, what 'division' scopes to, or how countOnly/totalCount affect the returned payload, leaving most calling decisions to guesswork.

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% and the description says nothing about any of the nine parameters (page, skip, order, fields, distinct, division, pageSize, countOnly, totalCount). Terms like 'distinct', 'countOnly', and 'division' are ambiguous without explanation, and the description contributes no meaning at all.

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?

The description states a specific verb+resource ('Find Titles') and immediately disambiguates the resource with the parenthetical 'salutation lookup values, e.g. Mr., Mrs., Dr.' This meaningfully separates it from the sibling job_titles_find, which is about job positions rather than salutations, though the description never explicitly names that distinction.

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 prerequisites, and no mention of an alternative such as titles_get for retrieving a single title by id. The 'find' verb implies a list/search operation, but the agent must infer that entirely from the name.

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