Skip to main content
Glama
Sign In
EasySourceFlow

EasySourceFlow

by john-ops-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

easysourceflow_cleanup

Destructive

Preview and safely remove old temporary artifacts from EasySourceFlow using a dry-run default to prevent accidental deletion.

Instructions

Preview or remove old EasySourceFlow temporary artifacts. Defaults to dry-run.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The description adds value beyond annotations by disclosing the default dry-run behavior and the option to preview before removal. This aligns with the destructiveHint=true annotation without contradiction.

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?

Single sentence, highly concise, with essential information front-loaded.

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?

Adequate for a simple tool with two parameters, but lacks description of return values or confirmation behavior. No output schema present.

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?

Schema coverage is 0%, so description must compensate. It adds context for 'dry_run' but not for 'days'. Only minimal inference from 'old' supports the days parameter.

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 tool previews or removes old temporary artifacts. It distinguishes from siblings like easysourceflow_backup by focusing on cleanup. However, it does not specify what qualifies as 'temporary artifacts'.

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 via 'Preview or remove' and notes default dry-run, but does not provide explicit guidance on when to use vs. alternatives 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