BagIQ MCP

detect_overlap

Detects redundant molds occupying the same flight slot or shot role, ranking pairs by overlap severity and recommending which disc to keep vs cut. Accepts discs list or a BagIQ share link.

Input Schema

TableJSON Schema

Name	Required	Description
`discs`	No	List of discs in the bag (minimum 2 discs, optional if share_url or share_id is provided)
`share_id`	No	Optional BagIQ short share ID (e.g. '4fisr8a7')
`share_url`	No	Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 8, 2026

changedInput schema / properties / discs / description

Previous value: -"List of discs in the bag (minimum 2 discs)"New value: +"List of discs in the bag (minimum 2 discs, optional if share_url or share_id is provided)"

addedInput schema / properties / share_id

Added value: +{
+  "description": "Optional BagIQ short share ID (e.g. '4fisr8a7')",
+  "type": "string"
+}

addedInput schema / properties / share_url

Added value: +{
+  "description": "Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "discs"
-]
```

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool detects overlaps, ranks pairs, and recommends keep/cut decisions, which implies a read-only analysis workflow. It does not mention side effects, but none are indicated by the described behavior.

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?

Two compact sentences with no filler: the first states the core purpose and output, the second states accepted input forms. Every clause contributes useful information.

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?

The description is sufficient for an agent to understand what the tool does, what inputs are acceptable, and what kind of output to expect. With no output schema, it helpfully states the output as ranked overlapping pairs with keep/cut recommendations. It could be more explicit about exact return formatting, but that is a minor gap.

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%, so the description does not need to restate parameter details. The phrase 'Accepts discs list or a BagIQ share link' adds a small amount of orientation by clarifying the two input modes, but it mostly paraphrases what the schema already documents.

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 uses a specific verb ('Detects') with a clear resource ('redundant molds occupying the same flight slot or shot role') and states the tool's unique output ('ranking pairs by overlap severity and recommending which disc to keep vs cut'). This clearly differentiates it from siblings like find_bag_gaps or recommend_bag_fillers.

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?

The description naturally signals when to use the tool: whenever redundancy or overlap between discs in a bag is the concern. It gives clear context for selection, though it does not explicitly name alternative tools or state when not to use it.

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

All BagIQ MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?