Skip to main content
Glama
Sign In
fintable-mcp

fintable-mcp

by jasoncbraatz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fintable_list_rules

Read-onlyIdempotent

List categorization rules for auto-categorizing transactions. Each rule matches a description pattern to a category. Supports pagination for browsing.

Instructions

List all categorization rules. Rules auto-categorize transactions based on description patterns.

Each rule has a pattern (e.g., 'Home Depot') and a target category (e.g., 'COGS'). When 'Run All Rules' is triggered, transactions matching the pattern get categorized.

Args: params: page number for pagination (rules are paginated).

Returns: str: JSON list of rules with id, pattern, category, and display text.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by explaining the purpose of rules, pagination behavior, and return format. No contradictions with 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?

The description is concise: three sentences covering purpose, context, and parameters. Front-loaded with purpose, no redundant information, every sentence earns its place.

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's simplicity (list with pagination) and the presence of annotations and output schema, the description is complete. It explains the rule concept, pattern/category, triggers, and return structure, leaving no gaps for an AI agent.

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 description mentions the 'params' argument as page number for pagination, which adds context to the schema's description. However, it could be more precise about the nested structure, and schema description coverage is low (0%), so description partially compensates.

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 'List all categorization rules' and explains the function of rules, distinguishing it from create/delete/run siblings. It provides specific verb and resource, and includes pagination detail.

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?

The description implies using this tool to view existing rules but lacks explicit guidance on when to use it versus alternatives like fintable_create_rule or fintable_run_all_rules. No exclusions or when-not-to-use are mentioned.

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