Skip to main content
Glama
Sign In
fiken-mcp

fiken-mcp

by gronnmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fiken_get_invoice_draft

Read-only

Retrieve a specific invoice draft by its ID from Fiken. Use this to view or process individual draft invoices.

Instructions

Returns a specific invoice draft

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": {
      "draftId": "<draftId>"
    },
    "name": "fiken_get_invoice_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotation 'readOnlyHint: true' already indicates this is a read operation. The description adds no further behavioral context (e.g., error handling, response structure). It does not contradict the annotation, but provides minimal extra value.

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 sentence with no unnecessary words, efficiently conveying the core functionality. For a simple retrieval tool, this is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (one parameter, no output schema, no nested objects), the description is minimally sufficient. However, it could mention the return format or that the draft must exist, which would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

The description does not explain the 'draftId' parameter. Schema coverage is 0%, yet the description provides no additional meaning, leaving the agent unsure about what value to provide.

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 clearly states the verb 'Returns' and the resource 'specific invoice draft', making the purpose understandable. However, it lacks explicit differentiation from sibling tools like 'fiken_list_invoice_drafts', though the word 'specific' implies it returns a single draft by ID.

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 given on when to use this tool versus alternatives such as 'fiken_list_invoice_drafts' or 'fiken_create_invoice_draft'. The description does not mention any prerequisites or exclusions.

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