Skip to main content
Glama

Lovie Company Formation

Suggest Transfer Pairs

accounting_suggest_transfer_pairs
Read-only

Rank the journal entries that could be the other half of a transfer between the company's own accounts: opposite direction, same amount, different instrument, dated within a few days. Writes nothing — a person confirms a pair in the app.

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": {
      "companyId": "<companyId>",
      "journalEntryId": "<journalEntryId>"
    },
    "name": "accounting_suggest_transfer_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.
journalEntryIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / candidates / items / properties / blockedReason
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Writes nothing — a person confirms a pair in the app,' which adds the human-in-the-loop workflow that annotations cannot express. It also discloses the heuristics used for ranking, which is genuine behavioral context beyond the structured fields.

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?

Two sentences, no filler, and the core purpose plus matching criteria are front-loaded before the read-only reassurance. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, matching heuristics, and the no-write/human-confirmation behavior. The only remaining gap is parameter-level meaning, which is minor given the small two-parameter surface.

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%, so the baseline is 3. The description implies that the input is a single journal entry whose counterpart is being sought, but it never explains what companyId or journalEntryId mean or how the two interact, and the schema's own descriptions are only generic 'UUID value wrapper' strings.

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?

The description states a specific verb (rank) and resource (journal entries that could be the other half of a transfer) and enumerates the matching criteria: opposite direction, same amount, different instrument, within a few days. It is highly distinctive from siblings like suggest_statement_matches, though it does not explicitly name a sibling to differentiate against.

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

Usage Guidelines3/5

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

The matching criteria imply when the tool is applicable (finding the counterpart entry of an internal transfer), but there is no explicit when-to-use statement, no exclusions, and no named alternative such as suggest_statement_matches or get_similar_review_items. Usage must be inferred.

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.