Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

contacts_get

Retrieve a contact record by ID to look up Macola 10 contact details.

Instructions

Get the Contact 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": "contacts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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, yet it says nothing about what happens when the ID does not exist, whether the call is read-only, or what shape the response takes. For a lookup tool this is a meaningful gap, though the read semantics are strongly implied by "Get".

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 short sentence with the key information front-loaded and no wasted wording. It is efficient, though "for a particular entry" is slightly redundant filler.

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 one-parameter read tool with no output schema, the definition is minimally adequate: the agent can call it correctly. It stops short of describing the returned contact fields or not-found behavior, which would be needed for full confidence.

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 documented as "Contact ID," so the schema already does the work. The description's phrase "by specifying its ID" merely restates it without adding format, type, or sourcing guidance.

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 and resource ("Get the Contact") plus the lookup key (ID), so the agent knows this is a single-record retrieval. It does not distinguish itself from the sibling contacts_find, which likely serves the search use case, leaving the boundary implicit.

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?

No guidance on when to use this versus contacts_find or contacts_create/update. The only implied condition is "you already have an ID," which the agent must infer from the parameter rather than from the text.

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