Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

List funding sources

list_funding_sources
Read-only

Retrieve available funding sources—balances, cards, banks, and invoices—that can pay for rewards. Use it to identify which source to charge before sending a reward.

Instructions

List the funding sources (balance, card, bank, invoice) that can pay for rewards. Balances in this list can be a little stale.

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": "list_funding_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds one genuinely useful behavioral caveat — that balances can be 'a little stale' — but says nothing about ordering, freshness window, rate limits, or whether all funding types are always returned.

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?

Two short sentences, front-loaded with the resource and its purpose, with the staleness caveat placed as a follow-up note. No redundant or filler wording.

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?

This is a simple, parameterless read-only listing, and annotations cover the safety profile while the description covers scope and the staleness caveat. Absent an output schema, a brief note on the shape of returned entries would be the only marginal improvement.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The enumerated source types give useful context about what the returned entries represent.

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 ('List') and resource ('funding sources'), and even enumerates the source types (balance, card, bank, invoice) plus their purpose ('can pay for rewards'). It is clearly not the same as list_rewards or list_campaigns, though it does not explicitly name a sibling it must be distinguished from.

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 implied by 'that can pay for rewards', which tells the agent this is the discovery step before payment-related operations. However, there is no explicit when-to-use vs when-not, and no mention of what to do if a needed source is absent or stale.

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