Skip to main content
Glama
deenesjakoruzh
Meh-S-Eze

MCP YNAB Server

by Meh-S-Eze
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

_find_transaction_by_id

Locate specific transactions using their unique ID and ID type within the MCP YNAB Server, enabling precise retrieval and management of financial data.

Instructions

Find a transaction by its ID and ID type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_typeYes
transaction_idYes
transactionsYes

Implementation Reference

  • src/mcp_ynab/server.py:546-563 (helper)
    Helper function that implements the logic to find a transaction by ID, import_id, transfer_transaction_id, or matched_transaction_id.
    def _find_transaction_by_id(
    transactions: List[TransactionDetail], transaction_id: str, id_type: str
) -> Optional[TransactionDetail]:
    """Find a transaction by its ID and ID type."""
    for txn in transactions:
        if (
            (id_type == "id" and txn.id == transaction_id)
            or (id_type == "import_id" and txn.import_id == transaction_id)
            or (
                id_type == "transfer_transaction_id"
                and txn.transfer_transaction_id == transaction_id
            )
            or (
                id_type == "matched_transaction_id" and txn.matched_transaction_id == transaction_id
            )
        ):
            return txn
    return None

Tool Definition Quality

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'finds' a transaction, which suggests a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns errors for missing IDs, or handles deleted transactions. The description lacks critical behavioral context for a lookup tool, leaving gaps in understanding how it behaves in practice.

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 description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a simple lookup tool, though it could be more informative. The structure is straightforward, but it lacks front-loading of critical details like parameter explanations or usage context.

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

Completeness2/5

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

Given the complexity (3 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return format, error handling, or how parameters interact. For a tool with undocumented parameters and no structured guidance, the description should provide more context to compensate, but it offers only a basic overview, leaving significant gaps for an agent to understand and use the tool effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but fails to do so. It mentions 'ID and ID type' but doesn't explain what 'ID type' means (e.g., transaction ID vs. import ID), the format of 'transaction_id', or the purpose of the 'transactions' parameter. With 3 undocumented parameters, the description adds minimal value beyond restating parameter names, leaving semantics unclear.

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 states the tool's purpose ('Find a transaction by its ID and ID type'), which is clear but generic. It specifies the verb ('Find') and resource ('transaction'), but doesn't differentiate from sibling tools like 'get_transactions' or explain what makes this lookup unique (e.g., exact ID match vs. filtering). The purpose is understandable but lacks specificity about scope or distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_transactions' (which might list multiple transactions) or 'get_transactions_needing_attention'. The description implies it's for exact ID-based retrieval, but it doesn't explicitly state prerequisites, exclusions, or compare to siblings. Usage is implied from the name and description alone, with no explicit instructions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Meh-S-Eze/ynab-mcp-client2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server