Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Find Customers

merit_find_customers
Read-only

Find customers by name or registry code and return contact details, payment terms, and comments for bookkeeping. Filter by exact registry code or partial name and cap returned rows.

Instructions

Customers with contact details, payment terms and comments.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the name; empty lists all
limitNoMax rows to return (totals still cover all)
reg_noNoExact registry code (overrides name)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe external read. The description adds that customer records include contact details, payment terms, and comments, which helps an agent understand the data shape, but it does not disclose operational traits such as pagination behavior or how totals interact with limits.

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?

The definition is a single efficient sentence with no wasted words. However, it is structured as a fragment and does not front-load the action, so clarity is slightly reduced.

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

Completeness4/5

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

For a simple read-only lookup with complete schema descriptions, safety annotations, and an output schema, the description covers the essential data content. The main remaining gap is that it never explicitly states the retrieval action or filtering capability, but the structured fields compensate heavily.

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 description coverage is 100%, so the schema already explains partial-name matching, the limit, and exact registry-code override behavior. The description adds no parameter meaning beyond the schema, making the baseline score of 3 appropriate.

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

Purpose3/5

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

The description identifies the resource (customers) and the kinds of data returned, but it is a noun phrase without an action verb such as 'find' or 'list'. An agent must rely on the tool name to understand that this is a retrieval operation, though the customer focus is unambiguous.

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 alternatives, no mention of filtering behavior, and no exclusions or prerequisites. The schema implies filtering by name or reg_no, but the description does not help an agent choose this tool over sibling lookup or report tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.