Skip to main content
Glama
dannyshaw

Pocketsmith MCP Server

by dannyshaw

pocketsmith_create_transaction

Create a new transaction by providing account ID, payee, amount, and date, with optional category, labels, notes, and transfer flag.

Instructions

Create a new transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transaction_account_idYesThe transaction account ID
payeeYesThe payee name
amountYesThe transaction amount (negative for debit, positive for credit)
dateYesThe transaction date (YYYY-MM-DD)
is_transferNoWhether this is a transfer between accounts
labelsNoLabels to assign to the transaction
category_idNoCategory ID to assign
noteNoNote for the transaction
memoNoMemo for the transaction
needs_reviewNoWhether the transaction needs review
Behavior2/5

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

No annotations are present, and the description fails to disclose behavioral traits like mutation effects, idempotency, or confirmation steps, leaving the agent without crucial safety information.

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 with a single, clear sentence, but could benefit from a brief structure like listing key intended use cases without becoming verbose.

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?

Given the tool has 10 parameters and no output schema, the description is too sparse, failing to explain return behavior, constraints, or post-creation effects, which are necessary for an agent to use it correctly.

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 input schema has 100% parameter description coverage, so the description adds no additional meaning. Baseline score of 3 is appropriate as the schema already provides detailed parameter semantics.

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

Purpose4/5

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

The description 'Create a new transaction' clearly states the verb (create) and resource (transaction), but lacks differentiation from sibling tools like 'pocketsmith_update_transaction' or 'pocketsmith_categorize_transaction'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as when a transaction should be created vs updated or categorized.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dannyshaw/pocketsmith-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server