Skip to main content
Glama
Sign In
fiken-mcp

fiken-mcp

by gronnmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fiken_create_credit_note_counter

Create the first credit note number counter to enable automatic sequential numbering for credit notes.

Instructions

Creates the first credit note number counter

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fiken_create_credit_note_counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations indicate it is a write operation (readOnlyHint=false), which the description echoes. However, it does not disclose what happens if a counter already exists, any side effects, or 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?

The description is a single, clear sentence with no extraneous information, but it could be slightly improved by front-loading the primary action.

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?

For a simple tool with one parameter and no output schema, the description is insufficient. It omits details about the effect on numbering sequences, error states, and related retrieval tools.

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?

The lone parameter 'value' is not explained: its purpose (starting number, increment, etc.) and optionality are ambiguous. With 0% schema coverage, the description should compensate but does not.

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 it creates the first credit note number counter, distinguishing it from sibling tools like fiken_create_invoice_counter and fiken_create_offer_counter.

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 on when to use this versus alternatives such as fiken_get_credit_note_counter, nor any prerequisites or conditions (e.g., whether a counter can be re-created).

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