Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Find Vendors

merit_find_vendors
Read-only

Find vendors by partial name or exact registry code, returning contact details, bank accounts, and payment terms for supplier lookup and bookkeeping.

Instructions

Vendors (suppliers) with contact details, bank account and payment terms.

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_vendors"
  }
}

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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds nothing further: no note on pagination, no statement that limit caps rows while totals span all matches, no hint that results may be large or how name matching behaves. Those facts live only in the schema, not the prose.

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

Conciseness3/5

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

It is a single short fragment with no wasted words, but that brevity comes at the cost of structure: without a verb or a lead clause it reads as a data label rather than an instruction. It is under-specified rather than efficiently concise.

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?

An output schema exists and all three parameters are fully documented, so the structured fields carry most of the load. Still, for a searchable vendor-lookup tool the description never says it is a search, nor what the typical use case is, leaving the agent to reconstruct intent from the tool name.

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 each parameter carries its own description, including the important "reg_no overrides name" precedence rule and the limit/totals caveat. The description contributes nothing beyond the schema, so the baseline of 3 applies.

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 and its payload ("Vendors (suppliers) with contact details, bank account and payment terms"), which tells an agent what data this returns. However, it is a bare noun phrase with no verb, so it never states that the tool searches/finds vendors, and it gives no differentiation from the sibling merit_find_customers beyond the word "suppliers".

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, no prerequisites, and no mention of any alternative (e.g. a customer-lookup sibling). An agent must infer from the tool name alone that this is the lookup path for supplier master data.

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