Skip to main content
Glama
Sign In
Mintline MCP Server

Mintline MCP Server

by mintlineai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

unskip_transaction

Revert a skipped transaction to re-require a receipt. Undo the skip and mark the transaction as needing a receipt again.

Instructions

Unskip transaction. Undo a skip — mark a transaction as needing a receipt again.

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": {
      "id": "<id>"
    },
    "name": "unskip_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransaction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.9

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It lacks details on side effects (e.g., what if already unskipped), permissions, or error conditions. The behavioral info is minimal.

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 extremely concise at two sentences, front-loaded with the action and explanation. Every word adds value without redundancy.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description is adequate but does not cover edge cases like idempotency or error handling. It meets minimum viability.

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

Parameters3/5

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

Schema coverage is 100% and the parameter 'id' is described as 'Transaction ID' in the schema. The description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 action: 'Unskip transaction' and explains the effect: 'Undo a skip — mark a transaction as needing a receipt again.' It is specific and distinguishes from sibling tool 'skip_transaction'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after a skip, but does not explicitly state when to use or when not to use it. No alternatives are mentioned, though sibling tools like skip_transaction provide context.

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