Skip to main content
Glama

List product gaps

list_gaps
Read-onlyIdempotent

Products people asked for that none of the closest products checked offer, with the original ask, requirements and products checked, plus agent-search misses repeated by 3+ requests from 2+ agents. No key: 10-gap preview. With a free key (POST /v1/keys): full rows, paged by cursor, counts 1 call. A gap is worth a closer look, never verified demand.

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

Input Schema

NameRequiredDescriptionDefault
qNoFilter by words in the gap or its requirements, e.g. 'wide fit boots'.
limitNoWorkspace key only.
cursorNonext_cursor from the previous call. Workspace key only.

Output Schema

NameRequiredDescriptionDefault
codeNo
gapsNo
agent_gapsNo
next_cursorNo
upgrade_urlNo
human_messageNo
credits_chargedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • removedInput schema / properties / category
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / class
      Removed value: -{
      -  "description": "Comma list of absent, exists_hard_to_find, unverified.",
      -  "type": "string"
      -}
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from the previous page."New value: +"next_cursor from the previous call. Workspace key only."
    • removedInput schema / properties / detail
      Removed value: -{
      -  "default": "summary",
      -  "description": "summary = L0 (1 credit per call); full = L1 (1 + 10 credits per scored row).",
      -  "enum": [
      -    "summary",
      -    "full"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / include
      Removed value: -{
      -  "description": "Also return unscored leads (L0 only, verdict null).",
      -  "enum": [
      -    "unscored"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / limit / default
      Previous value: -20New value: +50
    • addedInput schema / properties / limit / description
      Added value: +"Workspace key only."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +100
    • removedInput schema / properties / min_score
      Removed value: -{
      -  "maximum": 100,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / properties / q / description
      Previous value: -"Words that must appear in the gap label or requirements."New value: +"Filter by words in the gap or its requirements, e.g. 'wide fit boots'."
    • removedInput schema / properties / since
      Removed value: -{
      -  "description": "ISO date or epoch ms; only gaps with an ask since then.",
      -  "type": "string"
      -}
    • removedInput schema / properties / sort
      Removed value: -{
      -  "default": "score",
      -  "enum": [
      -    "score",
      -    "newest",
      -    "asks",
      -    "rising"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / source
      Removed value: -{
      -  "description": "Comma list of community_ask, agent_search, store_search, bot_research.",
      -  "type": "string"
      -}
    • removedInput schema / properties / trend
      Removed value: -{
      -  "description": "Comma list of rising, steady, cooling.",
      -  "type": "string"
      -}
    • removedInput schema / properties / verdict
      Removed value: -{
      -  "description": "Comma list of go, maybe, no-go.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / agent_gaps
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / detail
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / licence
      Removed value: -{
      -  "type": "string"
      -}
  2. Added
  3. Removed
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already state readOnly, idempotent, closed-world access, so the remaining gaps are the access model and trust level. The description adds both: an unauthenticated preview is capped at 10 gaps, a key unlocks full paged rows, and the call counts as one request. The closing caveat that a gap is 'worth a closer look, never verified demand' correctly warns the agent not to treat results as confirmed demand.

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 information is front-loaded and there is little outright filler, but the opening sentence is an overloaded clause stack and fragments like 'counts 1 call' require interpretation. Splitting the access-tier facts into a clean sentence would improve scanability without losing content.

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?

An output schema exists, so the description need not describe return shapes. For a zero-required-parameter read tool, it covers the access tiers, paging model, and the interpretive caveat on results. Minor omissions: whether the q filter applies to the unauthenticated preview and how rows are ordered.

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 every parameter already carries a description, bounding limit to 1-100 and explaining that cursor takes next_cursor from the prior call. The description confirms cursor-based paging and implies that limit and cursor apply only to keyed workspaces, matching the schema notes, but adds no new syntax or filtering semantics. Baseline 3 is appropriate.

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 names a specific resource: products requested that no close product offers, including the original ask, requirements, products checked, and repeated agent-search misses. That is far more concrete than the title alone. It does not, however, distinguish itself from siblings like search_products or find_retailers, and the single run-on sentence makes the core object slower to grasp than it should be.

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 explains the access tiers: a no-key 10-gap preview versus full paged rows with a free key. That is genuinely useful for deciding whether to call it. What is missing is explicit guidance about when to use this instead of search_products or find_retailers, and when a gap list is the wrong tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources