Skip to main content
Glama
Sign In
fintable-mcp

fintable-mcp

by jasoncbraatz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fintable_run_all_rules

Idempotent

Automatically categorize transactions by applying all rules in priority order to uncategorized entries.

Instructions

Run all categorization rules to auto-categorize transactions.

This triggers the same action as clicking 'Run All Rules' in the Fintable UI. All rules are applied to uncategorized transactions in priority order.

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": {
      "params": "<params>"
    },
    "name": "fintable_run_all_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations by stating it applies rules to uncategorized transactions in priority order and mimics a UI action. No contradiction with annotations (idempotentHint=true aligns).

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?

The description is concise (3 sentences), front-loads the main purpose, and provides necessary detail without redundancy.

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?

Given the tool has no parameters, annotations are present, and an output schema exists (though not shown), the description fully explains the tool's function and behavior for agent invocation.

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 input schema has no actual parameters (only a required empty object). With 0 parameters, the baseline is 4. The description does not need to compensate for any missing parameter information.

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 clearly states the action (run all rules), resource (categorization rules), and result (auto-categorize transactions). It distinguishes from sibling tools like create_rule or list_rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context that it triggers the same action as clicking 'Run All Rules' in the UI, but does not explicitly state when not to use it or suggest alternatives. Still, the usage context is clear.

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

Deploy Server

Other Tools