Skip to main content
Glama

Truo

Recurring payments and upcoming bills

recurring_and_upcoming
Read-only

Detected recurring payments and income (bills, subscriptions, salary) with their cadence, typical amount, and predicted next date. "Upcoming" lists what is expected in the 35 days after the date the data is current as at, which every answer states. Predictions are estimates based on past cadence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recurring_and_upcoming"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfNo
noteNo
recurringNo
coveredPeriodNo
endedInPeriodNo
connectionNoticesNo
upcomingNext35DaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / connectionNotices
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "not": {}
      +        },
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      ]
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

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, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the 35-day forecast horizon, that answers state the as-at date the data is current to, and that predictions are estimates from past cadence rather than confirmed transactions.

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?

Three front-loaded sentences that each carry new information: the resource, the forecast window, and the estimation caveat. The clause 'which every answer states' is somewhat awkwardly attached but is not padding.

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

Completeness5/5

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

With zero parameters, an output schema, and full annotation coverage, the description needs only to explain what the output means and its limits. It does exactly that by defining the forecast horizon, the as-at date disclosure, and the estimate caveat, so nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters (schema coverage 100%), so the baseline for parameter semantics is 4; the description adds no parameter-level meaning because there is nothing to parameterize. It also does not note that the account/currency scope is implicit rather than selectable, which would have earned the top score.

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 resource (detected recurring payments and income: bills, subscriptions, salary) and what each item carries (cadence, typical amount, predicted next date). That is far more specific than the title alone, but it never contrasts itself with siblings such as income_and_expenditure or monthly_trend, so the agent must infer the boundary.

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?

Usage is only implied: the description clarifies what 'Upcoming' means (a 35-day forward window) and that predictions derive from past cadence, which suggests when the tool is appropriate. It gives no explicit when-to-use, when-not-to-use, or alternative tool for backward-looking or aggregated income analysis.

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