Skip to main content
Glama

get_financial_pnl

Read-onlyIdempotent

Retrieve summarized expenses, income, cash flow, and profit-and-loss details. Requires farmId and apiKey authorization.

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_financial_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoOptional month filter (e.g. 2026-09)
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new fact beyond the structured fields – that farmId and apiKey authorization are required – but says nothing about the effect of includeSuperseded or the aggregation granularity.

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?

Two tight sentences with the capability stated first and the prerequisite second; nothing is padded. Minor noise: apiKey is described as required but is not in the input schema, which is a small distraction in an otherwise lean definition.

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 tool with no output schema, the description does list the returned content categories (expenses, income, cash flow, P&L), which is the key missing context. It stops short of explaining the aggregation level or how superseded entries affect totals.

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%, so month, farmId, and includeSuperseded are already documented in the schema. The description only restates farmId as required and adds no format or behavioral detail about the optional filters, so baseline 3 applies.

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?

Specific verb 'Retrieve' paired with a concrete resource set: summarized expenses, income, cash flow, and P&L. An agent can distinguish this from raw-data siblings like get_transactions, though the description never names that boundary 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?

No when-to-use guidance, no exclusions, and no routing against get_transactions, get_orders, or get_time_logs, which are the obvious adjacent financial tools. The only contextual hint is the authorization prerequisite.

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