fiken-mcp

fiken_list_order_confirmations

Read-only

Retrieve a paginated list of all order confirmations for your company. Control results with page and page size parameters.

Instructions

Returns all order confirmations for the company

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

Input Schema

Name	Required	Description	Default
`page`	No
`pageSize`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds no further behavioral traits (e.g., pagination behavior, rate limits). It neither contradicts annotations nor provides additional transparency beyond them.

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?

Single sentence is concise and front-loaded with the core purpose. However, it omits important details about pagination and parameters, making it less helpful. The sentence earns its place but could be more informative without sacrificing brevity.

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 no output schema and zero param descriptions, the description is incomplete. It does not explain pagination, return format, or how this tool fits among many sibling tools (e.g., invoices, offers). Significant gaps remain 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.

Parameters2/5

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

Schema has 0% description coverage for the two integer parameters (page, pageSize). The description does not explain their meaning or usage, leaving the agent to infer from names alone. The description should compensate but fails to do so.

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?

Description clearly states 'Returns all order confirmations for the company,' specifying a verb and resource. It distinguishes from the sibling 'get_order_confirmation' (single) and other list tools. However, the word 'all' may be misleading since it supports pagination via page/pageSize, but the description does not clarify this.

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 tool versus alternatives like 'fiken_get_order_confirmation' or other list tools. The description fails to mention that this is for listing multiple confirmations or any context about pagination.

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

Deploy Server