Skip to main content
Glama
Sign In

FundingTracker

by app.fundingtracker
OverviewDiscussionsAdmin

List my deals

list_my_deals
Read-onlyIdempotent

List the signed-in user's deals in FundingTracker (merchant cash advances, loans, lines of credit): funder, financing type, amounts, amount paid, remaining balance, payment amount and frequency, and projected payoff date. Requires signing in to FundingTracker.

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

Input Schema

NameRequiredDescriptionDefault
include_closedNoAlso list closed (paid off or bought out) deals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds a meaningful auth precondition ('Requires signing in to FundingTracker') plus what information the listing exposes. It does not discuss pagination or ordering, but the added behavioral context is useful beyond the annotations.

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 tight sentences: the first front-loads the listing scope and returned fields, and the second adds the authentication precondition. There is no redundant or filler text.

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 simple read-only list tool with rich annotations and complete schema coverage, the description is largely sufficient, especially because it enumerates the returned deal fields in the absence of an output schema. Minor gaps remain around pagination and ordering, but the core calling information is present.

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%, and the single parameter include_closed is fully documented in the schema with its default. The description adds no parameter-level detail, which is acceptable given the schema already does that work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('List the signed-in user's deals') and scopes the domain with concrete financing types and returned fields. An agent can distinguish this from singular deal retrieval and from funder/alert tools without opening the schema.

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?

It implies usage by saying it lists the signed-in user's deals and notes an authentication prerequisite, but it does not explicitly say when to use this versus siblings like get_my_deal or list_my_alerts. The context is clear, but alternatives and exclusions are only inferable.

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

All FundingTracker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources