fiken-mcp

fiken_get_purchase

Read-only

Retrieve a specific purchase by ID to get its details from Fiken accounting records.

Instructions

Returns a specific purchase by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "purchaseId": "<purchaseId>"
    },
    "name": "fiken_get_purchase"
  }
}

Input Schema

Name	Required	Description	Default
`purchaseId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description does not add any behavioral context beyond what annotations already declare (readOnlyHint=true). It omits details like error handling, authentication needs, or whether the purchase ID is scoped to a company, which are important for safe invocation.

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

Conciseness5/5

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

The description is a single, efficient sentence (6 words) that conveys the core action without any fluff, earning its place.

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 one parameter and no output schema, the description is too sparse; it does not specify the return value shape, prerequisites (e.g., company context), or behavior on missing ID, leaving the agent with incomplete context.

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?

With 0% schema description coverage, the description only says 'by ID', which adds minimal value since the parameter name 'purchaseId' is self-explanatory. It does not specify format, constraints, or how the ID relates to the purchase resource.

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 verb 'Returns' and the resource 'a specific purchase', with the identifier 'by ID', making the purpose precise and distinguishing it from sibling tools like fiken_list_purchases (list) and fiken_get_purchase_draft (related but different entity).

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; for example, it does not explain when to use this over fiken_list_purchases or fiken_get_purchase_draft, leaving the agent to infer from names alone.

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

Deploy Server