Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_files_from_module

Remove multiple files from modules in a single batch operation, skipping non-existent entries and reporting modules left empty.

Instructions

Batch remove multiple files from modules. More efficient than multiple remove_file_from_module calls. Skips non-existent entries, reports modules left empty.

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": {
      "links": "<links>"
    },
    "name": "remove_files_from_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYesList of [file_id, module_id] tuples to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds valuable context: it skips non-existent entries and reports modules left empty. This goes beyond annotations without contradicting them.

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 concise sentences, all earning their place. Front-loaded with the action, no wasted words.

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 tool with one required parameter and no output schema, the description covers key behaviors (efficiency, skipping, reporting). It lacks return value details, but given the simplicity, it is fairly complete.

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% with a clear description for the 'links' parameter. The description adds little beyond 'batch' context, so a baseline 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 'Batch remove multiple files from modules', using specific verbs and resources. It distinguishes itself from the sibling tool 'remove_file_from_module' by highlighting efficiency for multiple removals.

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 use for multiple removals by stating it's more efficient than multiple single calls, but it lacks explicit when-to-use or when-not-to-use guidance. No mention of prerequisites or alternatives beyond the single-removal sibling.

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