mcp-medusa

Overview Schema Source Related Servers Discussions Admin

resolve_and_add_anime

Resolve an anime by title or ID, compare its score to the threshold, and add it to Medusa when validated. Use dry-run mode to preview the resolution before executing.

Instructions

Resolve and optionally add one anime. Dry-run unless execute is true.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`title`	No
`mal_id`	No
`source`	No	myanimelist
`execute`	No
`root_dir`	No	/media/videos/Anime
`min_score`	No
`score_gap`	No
`directory_name`	No
`verify_attempts`	No
`verify_delay_seconds`	No
`initial_release_group`	No	SubsPlease
`fallback_release_groups`	No
`release_group_fallback_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.0.23Aug 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / directory_name / title
```
Removed value: -"Directory Name"
```
- removedInput schema / properties / execute / title
```
Removed value: -"Execute"
```
- removedInput schema / properties / fallback_release_groups / title
```
Removed value: -"Fallback Release Groups"
```
- removedInput schema / properties / initial_release_group / title
```
Removed value: -"Initial Release Group"
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / mal_id / title
```
Removed value: -"Mal Id"
```
- removedInput schema / properties / min_score / title
```
Removed value: -"Min Score"
```
- removedInput schema / properties / release_group_fallback_days / title
```
Removed value: -"Release Group Fallback Days"
```
- removedInput schema / properties / root_dir / title
```
Removed value: -"Root Dir"
```
- removedInput schema / properties / score_gap / title
```
Removed value: -"Score Gap"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- removedInput schema / properties / title / title
```
Removed value: -"Title"
```
- removedInput schema / properties / verify_attempts / title
```
Removed value: -"Verify Attempts"
```
- removedInput schema / properties / verify_delay_seconds / title
```
Removed value: -"Verify Delay Seconds"
```
- removedInput schema / title
```
Removed value: -"resolve_and_add_animeArguments"
```
- removedOutput schema / title
```
Removed value: -"resolve_and_add_animeDictOutput"
```
First observedv0.1.0Jun 25, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose the critical dry-run behavior and the execute flag that switches to a mutating add. However, it does not explain side effects of adding, how resolution works, or whether filesystem/mal changes occur beyond the parameter names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one sentence and is front-loaded with the essential action and the dry-run caveat. No filler is present, but it is too terse for a tool with this many parameters and no schema documentation.

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

Completeness2/5

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

The description is incomplete for a 14-parameter tool with no schema descriptions. It omits the resolution process, criteria such as min_score and score_gap, release group fallback behavior, and filesystem implications. The presence of an output schema does not compensate for the missing input semantics.

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 description coverage is 0%, and the description adds almost no explanation of the 14 parameters. It only gives meaning to execute ('dry-run unless execute is true'); the rest of the parameters—mal_id, limit, score_gap, root_dir, release groups—remain unexplained.

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 explicitly states the action: resolve and optionally add one anime, with a dry-run default unless execute is true. This is a specific verb plus resource ('anime') and helps distinguish it from broad tools like bulk_add_anime, though it does not explicitly differentiate from add_anime or resolve_anime_title.

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 a dry-run-first workflow: run without execute to preview, then set execute=true to actually add. It gives the central usage condition, but does not provide guidance on when to choose this tool over the sibling add_anime, resolve_anime_title, or bulk_add_anime.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.