finance

Debt Payments: Create debt-payment rule

create_debt_payment_rule

    Create a rule that auto-matches withdrawals on an asset account to a debt account.

    When a transaction on `source_account_id` has a description containing
    the `description_pattern` (case-insensitive substring), the system
    creates a pending debt payment that the user can confirm or reject.
    After the configured threshold of confirmations, matches auto-apply.

    Args:
        source_account_id: Asset account the payment leaves from (e.g. checking)
        debt_account_id: Debt account the payment reduces (e.g. mortgage)
        description_pattern: Substring to match on the source transaction (<=200 chars)

    Returns:
        Created or reactivated rule details

Input Schema

TableJSON Schema

Name	Required	Description	Default
`debt_account_id`	Yes
`source_account_id`	Yes
`description_pattern`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Reveals non-obvious behavior beyond the readOnlyHint=false annotation: matched transactions create pending debt payments that users confirm or reject, and matches auto-apply only after a configured threshold. This gives the agent important expectations about side effects and workflow.

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?

Front-loaded with the core purpose, followed by a compact Args block and a Returns line. The length is justified because the deferred matching workflow is genuinely complex; no sentence is filler.

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 mutation tool with no output schema, it covers the key mechanics needed to call correctly: source account, debt account, matching pattern, pending-payment lifecycle, and auto-apply behavior. It leaves the threshold configuration and duplicate/reactivation details somewhat implicit, but the provided guidance is sufficient for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates by explaining all three parameters with practical examples (checking, mortgage), the substring match semantics, and the 200-character limit. Each parameter gains real meaning beyond its schema type.

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: 'Create a rule that auto-matches withdrawals on an asset account to a debt account.' It goes beyond the title by explaining the matching behavior and differentiates this creation tool from update/delete/list rule 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?

Provides clear context for when to use the tool: when the user wants automatic matching of asset-account withdrawals to debt accounts via a description pattern. It does not explicitly name alternatives or exclusions, so it falls short of a 5.

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

All finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?