Skip to main content
Glama
Sign In
fintable-mcp

fintable-mcp

by jasoncbraatz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fintable_create_category

Create a new transaction category for Fintable to organize expenses or income. Optionally assign it to a group like Expense, COGS, or Income for structured categorization.

Instructions

Create a new transaction category in Fintable.

The category will appear in the categorizer sidebar and can be used in rules. Use group_header to place the category under a group (e.g., 'Expense', 'COGS', 'Income').

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Adds information about the category appearing in the sidebar and being usable in rules, beyond the annotations which indicate a write operation. Could mention prerequisites like required permissions.

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 sentences with clear front-loading of purpose. No unnecessary words, but could be slightly more structured.

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?

Given the simple tool and good annotations, the description covers the main behavioral aspects. Lacks mention of output format or potential duplicates.

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 adds context for group_header (placing under a group) but the schema already provides detailed descriptions for both parameters. Moderate added value.

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?

Clearly states the tool creates a new transaction category in Fintable, and distinguishes from bulk creation or rule creation siblings.

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?

Provides guidance on using group_header, but does not explicitly state when to use this single-category tool versus the bulk sibling fintable_create_bulk_categories.

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