Skip to main content
Glama

get_transactions

Read-onlyIdempotent

Retrieve manual general ledger expense, income, and equity transactions.

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": {
      "farmId": "<farmId>"
    },
    "name": "get_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional pagination limit
cursorNoOptional cursor
farmIdYesThe unique farm ID
includeSupersededNoInclude soft-deleted/superseded duplicate entries (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeSuperseded
      Added value: +{
      +  "description": "Include soft-deleted/superseded duplicate entries (default false)",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / includeSuperseded
      Removed value: -{
      -  "description": "Include soft-deleted/superseded duplicate entries (default false)",
      -  "type": "boolean"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / includeSuperseded
      Added value: +{
      +  "description": "Include soft-deleted/superseded duplicate entries (default false)",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds scope detail (manual, GL, three transaction categories) but says nothing about pagination behavior, result volume, or how superseded entries affect results — those live only in the schema.

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?

One front-loaded sentence with no filler, stating the resource and the transaction categories the agent needs to match against. Nothing is repeated from the annotations or 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 read-only, idempotent list tool with full schema coverage and no output schema, the definition covers what the tool returns conceptually. The only gap is behavioral detail around pagination and superseded-entry inclusion, both of which the schema partially carries.

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 description coverage is 100%, with all four parameters documented, so the baseline is 3. The description contributes no additional parameter meaning beyond the schema, not even hinting at the farmId scoping or cursor semantics.

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?

States a specific verb (Retrieve) and resource (manual general ledger transactions), narrowed to expense, income, and equity types. The word 'manual' usefully separates it from other ledger sources, though it does not name the write counterpart (log_manual_transaction) or the analytics sibling (get_financial_pnl) explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as log_manual_transaction for writes or get_financial_pnl for aggregates. The agent must infer that this is the read path for manually entered ledger entries.

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