Skip to main content
Glama

taxsort-mcp

by io.github.lonniev

taxsort_save_classifications

Bulk write classifications from the FE.

classifications is a JSON array of objects, each with:

  • id: raw_transaction_id

  • category, subcategory (required)

  • confidence, reason, merchant, description_override (optional)

  • classified_by: 'ai' | 'rule' | 'manual' (default 'ai')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubNoRequired. Your Nostr public key (npub1...) for credit billing.
dpop_tokenNo
session_idYes
classificationsNo[]

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided. The description labels the operation as a 'write' but does not disclose whether classifications are overwritten or merged, reversal possibilities, or billing implications beyond the npub note. Lacks detail on side effects.

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?

The description is concise, front-loads the purpose, and then details the classifications format with bullet points. No unnecessary words. Could split into sections but efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters and an output schema, the description only addresses one parameter (classifications) and its structure. It omits return values, effects on existing data, and billing details. Incomplete for a write tool.

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

Parameters2/5

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

Schema coverage is low (25%). The description explains the 'classifications' parameter structure in detail, adding significant value. However, it does not document 'npub', 'dpop_token', or 'session_id', leaving their semantics unclear despite the schema being sparse.

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 tool's verb ('write') and resource ('classifications'), indicating a bulk write operation. It distinguishes from sibling tools like taxsort_delete_classification and taxsort_reset_classifications by focusing on saving.

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 does not explicitly state when to use this tool versus alternatives (e.g., individual classification updates). It implies bulk saving but provides no guidance on prerequisites or when not to use.

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

All taxsort-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes and thorough descriptions. However, the sheer number (84) and some similarly named tools (e.g., check_balance vs check_authority_balance) could cause minor confusion for an agent.

Naming Consistency3/5

All tools share the 'taxsort_' prefix, but the naming pattern is inconsistent: some use verb_noun (check_balance), while others use noun_noun (account_statement) or other structures. This mixed convention reduces predictability.

Tool Count2/5

84 tools is excessive for typical MCP server coherence. While the domain is broad, many tools seem administrative (e.g., get_anthropic_key) and could be consolidated. The high count likely overwhelms agents.

Completeness4/5

The tool set covers the core tax classification workflow (import, classify, summarize) plus auxiliary systems (payments, credentials, coupons, notarization). Minor gaps exist (e.g., no CSV export), but overall coverage is comprehensive.

Resources