Skip to main content
Glama
Sign In
fiken-mcp

fiken-mcp

by gronnmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fiken_create_offer_counter

Set the starting number for offers by creating the first offer counter. Use this to initialize offer numbering in your Fiken account.

Instructions

Creates the first offer 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_offer_counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The description and annotations (readOnlyHint: false) indicate it is a write operation. However, it does not disclose consequences like error handling for duplicate counters, default behavior for the 'value' parameter, or any side effects. With minimal annotations, more behavioral context is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no fluff. However, it is arguably too concise, sacrificing clarity for brevity. The structure is clean but underinformative.

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's simplicity (one optional parameter, no output schema), the description should provide enough context for an agent to use it correctly. It fails to explain when to call it or what the parameter does. Sibling tools for counters are similar, yet no distinctions are made.

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 single integer parameter 'value' has no description (0% schema coverage). The tool description does not explain its meaning (e.g., starting number, increment step). This leaves the agent to infer, risking incorrect usage.

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

Purpose3/5

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

The description specifies a verb ('creates') and resource ('offer number counter'), but 'first' is ambiguous and does not distinguish from other counter creation tools like fiken_create_invoice_counter. The purpose is clear enough for a basic understanding but lacks specificity.

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 (e.g., fiken_get_offer_counter, other create_counter tools). Conditions such as whether the counter must be initialized before use or what happens if it already exists are absent.

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