Skip to main content
Glama

BagIQ MCP

by app.bagiq.data
OverviewDiscussionsAdmin

find_bag_gaps

Identifies missing shot shapes and unserved flight slots across BagIQ's 9 core slot targets (putter, midrange, fairway, and distance drivers), ranking voids by severity. Accepts discs list or a BagIQ share link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
discsNoList of discs in the bag (optional if share_url or share_id is provided)
share_idNoOptional BagIQ short share ID (e.g. '4fisr8a7')
share_urlNoOptional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / discs / description
      Previous value: -"List of discs in the bag"New value: +"List of discs in the bag (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"
-]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key behavior—identifying and ranking voids by severity—and implies read-only analysis. However, it does not describe side effects, external fetching from a share link, failure behavior, or how results are returned.

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?

The description is a single, front-loaded sentence that states purpose, scope, and accepted inputs without filler. Every part earns its place.

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?

The description is adequate for a straightforward analysis tool: it names the target slots and says voids are ranked. However, with no output schema, it does not explain the result structure, severity values, or how missing discs are represented, so an agent still has some uncertainty about the return.

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 description coverage is 100%, so the schema already documents all parameters. The description adds some value by summarizing that either a discs list or a BagIQ share link can be supplied, but it does not deepen parameter semantics beyond 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 action ('Identifies missing shot shapes and unserved flight slots') with a clear resource (BagIQ's 9 core slot targets) and a distinctive behavior (ranking voids by severity). This clearly differentiates it from siblings like detect_overlap 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 gives clear context: use this when you need to identify bag gaps against BagIQ's slot targets, and it specifies the accepted input modes (discs list or share link). It does not explicitly name alternative tools or when-not conditions, so it stops short of a 5.

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

All BagIQ MCP toolsInspect
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