Skip to main content
Glama
Sign In
Mintline MCP Server

Mintline MCP Server

by mintlineai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hide_transaction

Hide a specific transaction to remove it from matching and default views by providing its ID.

Instructions

Hide transaction. Hide a transaction from matching and default views.

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": "hide_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransaction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.9

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions hiding from views but does not disclose reversibility (though there is an 'unhide_transaction' sibling), permissions, side effects, or any other behavioral traits beyond the basic effect.

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, consisting of two short sentences that immediately state the tool's purpose and effect. No wasteful words.

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?

For a simple tool with one parameter, the description conveys core functionality but lacks usage guidelines and differentiation from similar siblings. It is minimally adequate but could be more helpful.

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 only parameter 'id' is already described in the schema. The description adds no additional meaning beyond what is provided, meeting the baseline for high coverage.

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 'Hide' and resource 'transaction', specifying that it hides from matching and default views, which distinguishes it from other tools like 'delete_transaction' or 'reject_match'.

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 like 'skip_transaction' or 'unmatch_transaction'. The description lacks context about appropriate scenarios or prerequisites.

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