Skip to main content
Glama
ISO 20022 Payment Evidence & Investigation MCP

ISO 20022 Payment Evidence & Investigation MCP

generate_test_message

Generate a synthetic test message. kind: 'pacs.008' or 'pacs.002'. defect (pacs.008): none, bad_iban, bad_bic, missing_creditor_name, bad_decimals, count_mismatch, injection_in_remittance, missing_creditor_address.

Instructions

Generate a synthetic test message. kind: 'pacs.008' or 'pacs.002'. defect (pacs.008): none, bad_iban, bad_bic, missing_creditor_name, bad_decimals, count_mismatch, injection_in_remittance, missing_creditor_address. reason_code is used for pacs.002.

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

Input Schema

NameRequiredDescriptionDefault
kindNopacs.008
defectNonone
reason_codeNoAC04

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The description establishes that the output is synthetic and can be deliberately defective, including an injection-in-remittance variant. With no annotations, however, it does not explicitly confirm that generation is side-effect free or that nothing is sent or persisted, and it leaves invalid-combination behavior unstated.

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

Conciseness5/5

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

The purpose is front-loaded, followed immediately by compact parameter guidance with no filler. The inline defect list is dense, but its length is justified because those values are absent from the structured schema.

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 three-parameter generator with an output schema, the supported kinds, defect modes, and parameter applicability are sufficient for most invocations, while defaults are already available in the schema. Missing side-effect assurances, reason_code's valid domain, and handling of unsupported combinations prevent full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds substantial value: it restricts kind to two values, enumerates eight defect settings scoped to pacs.008, and states that reason_code is used for pacs.002. It does not document valid reason_code values or explain the precise effect of each defect, so its compensation is strong but incomplete.

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?

"Generate a synthetic test message" gives a specific operation and resource, while the two supported kinds clarify that this generates pacs.008 or pacs.002 content. Its synthetic-generation role is distinguishable from parsing or validation siblings, but the description does not explicitly differentiate it from them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling the output a "synthetic test message" and listing intentional defects clearly establishes a testing or fixture-generation context, including negative test scenarios. There is no explicit when-not guidance or routing to siblings such as validate_message or parse_message.

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