Skip to main content
Glama

Triplicate – export documents

Read a letter of credit (MT700)

read_letter_of_credit
Read-only

Use when the user has the text of a letter of credit (SWIFT MT700). Read the text of a documentary credit (SWIFT MT700 as advised by the bank): credit number, dates, amount and tolerance, partial shipments and transhipment, latest shipment, ports, presentation period, goods, the documents required (each with how to make it) and additional conditions, plus a letter_of_credit object for create_trade_documents. It does not judge whether a bank will accept the documents. Nothing is stored.

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": {
      "text": "<text>"
    },
    "name": "read_letter_of_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe letter of credit as advised: SWIFT MT700 fields (:20:, :31D:, :32B: ...) or a bank advice with the field numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world behavior, but the description adds meaningful context: nothing is stored and the tool does not assess bank acceptance. It does not cover malformed-input behavior, but the added boundaries are useful.

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 trigger condition is front-loaded and every clause carries information, though the long field enumeration makes it denser than ideal. Nothing is wasted, but the single sentence packs many ideas.

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

Completeness5/5

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

No output schema exists, but the description enumerates the returned fields and names the handoff object for create_trade_documents, giving an agent enough to call and use the tool confidently.

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?

With a single required parameter and 100% schema coverage, the baseline is 3. The description echoes the expected MT700 format and mentions the resulting letter_of_credit object, but adds little syntax detail beyond the schema's own description.

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

Purpose5/5

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

States a specific verb and resource ('Read the text of a documentary credit (SWIFT MT700)') and enumerates the fields it extracts, so an agent knows exactly what the tool returns and how it differs from document-checking siblings.

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?

Front-loads an explicit trigger ('Use when the user has the text of a letter of credit') and states a boundary ('does not judge whether a bank will accept the documents'), though it does not explicitly name competing alternatives beyond pointing to create_trade_documents as a downstream consumer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources