Skip to main content
Glama
Sign In
tradingview-capture

tradingview-capture

by sunkailun1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

output_prune

Retain the current day's capture batches and list older output folders; set apply=true to move older batches to macOS Trash without permanent deletion.

Instructions

Keep the current day's capture batches and list the older ones under the output root; with apply=true move those older batch folders to the macOS Trash. Never deletes anything for good. keep_days counts today (1 keeps today only).

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

Input Schema

NameRequiredDescriptionDefault
applyNo
keep_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden and does well: it discloses that nothing is permanently deleted (folders go to the macOS Trash), which folders are affected, and that today's batches are protected. It omits permission requirements and what happens to non-batch content under the output root, but the core destructive-behavior disclosure is present.

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?

Three short sentences, front-loaded with the core operation and immediately followed by the destructive condition and the safety guarantee. Every clause carries information an agent needs.

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

Completeness4/5

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

For a two-parameter mutation tool with no annotations but with an output schema (so return values need not be described), the description covers scope, both modes, safety, and both parameter semantics. Minor gaps around permissions and exact listing behavior are tolerable.

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

Parameters4/5

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

Schema coverage is 0% (titles only), so the description must compensate and largely does: it explains apply=true triggers the Trash move, and clarifies the non-obvious semantics that keep_days counts today inclusively (1 = today only). Only the default values themselves are left to the schema.

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 states a specific verb and resource: keep today's capture batches, list older batches, and optionally move them to the Trash. It also names the scope ('under the output root'), so an agent can distinguish this cleanup operation from capture_* and diagnose siblings without opening the schema.

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

Usage Guidelines4/5

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

It clearly explains the two modes — default listing versus apply=true which performs the move — giving an agent a safe dry-run path. It doesn't name alternative tools or state explicit preconditions, but no sibling overlaps this function, so the guidance is sufficient.

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