Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

titles_get

Retrieve the title for a specific entry by providing its ID in Macola 10. Use this lookup to identify or verify titles when you have only the ID.

Instructions

Get the Title 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": "titles_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTitle ID

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 disclosure burden for a read operation. It does not state what happens on an unknown ID (error vs. empty), what fields the returned Title contains, or whether any permissions are required, leaving behavior largely opaque.

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 compact sentence with the verb and lookup key front-loaded and no filler. It is perhaps a touch terse for a tool with no annotations, but nothing is wasted.

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 trivial single-parameter lookup with no nested objects and no output schema, the definition is minimally adequate. It leaves the return value and failure behavior unexplained, which is a meaningful gap given the complete absence of annotations.

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% with a single required 'id' parameter already documented in the schema as 'Title ID'. The description restates that the ID identifies the entry but adds no format, source, or example detail beyond the schema.

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') and resource ('the Title') scoped to a particular entry identified by ID. It is clear what the tool returns, but it never distinguishes itself from siblings like titles_find or job_titles_get, so an agent cannot tell from the description alone which retrieval tool applies.

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 'by specifying its ID' implies the usage context: it is a direct lookup when an ID is already known. However, there is no explicit guidance on when to use this instead of titles_find for a search, and no prerequisites or exclusions are stated.

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