Skip to main content
Glama

Check a 'no' from the AI: find products, apps, competitors, ways to do it or counter-evidence

check_a_no
Read-onlyIdempotent

Searches for things that an answer said do not exist or cannot be done: products, apps, services, competitors, ways to do something (guides, workarounds, open-source fixes, procedures), or evidence about a factual "no" ("no study shows...", "that's not allowed", "you're not entitled to...").

Suited to questions such as "is there an app / tool / service that...", "are there competitors to...", "is there a way to...", "does X exist in my country / in my language / on Shopify", or a factual or rights question whose answer is "no".

It runs the given queries in parallel on the general web and, optionally, inside specific places: app stores (Apple App Store, Google Play, Chrome Web Store), plugin marketplaces (Shopify, WordPress), launch and startup sites (Product Hunt and others), social and business pages (LinkedIn, Facebook, Instagram), how-to sites and forums (Reddit, YouTube, GitHub, Stack Exchange, local-language forums), and facts / research / rights sources (Wikipedia, PubMed, arXiv, government and rights sites).

Parameters:

  • claim: the "no" being checked.

  • product_shape: what the product or method would do, for whom, through which channel or device.

  • queries: 4-20 varied queries (synonyms, functional descriptions, "alternatives to X", "how to X", "X workaround"), in English and the user's language.

  • marketplace_queries: 3-5 short keyword phrases (2-5 words, English) run inside each chosen place, e.g. "memoir WhatsApp bot".

  • places: only the places that fit the question (apps/tools -> app_stores, plugin_marketplaces, launch_and_startup_sites, social_and_business_pages; "how to" -> how_to_and_forums; laws, rights, research -> facts_research_and_rights). Fewer places is faster and cheaper.

Returns deduplicated results (title, URL, snippet, where found) and a coverage report: queries run, places searched and skipped, hits per place. A result has not been verified; "not found" in these places is not proof that something does not exist.

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": {
      "claim": "<claim>",
      "product_shape": "<product_shape>",
      "queries": "<queries>"
    },
    "name": "check_a_no"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesWhat the user is asking about or the claim being checked, e.g. 'There is no service that turns seniors' voice recordings into a memoir book'.
placesNoWhich special places to search besides the general web. Pick only the ones that fit the question (apps/tools -> app_stores, plugin_marketplaces, launch_and_startup_sites, social_and_business_pages; 'can I / how to' -> how_to_and_forums; laws, rights, research, history -> facts_research_and_rights). Omit to search all of them.
queriesYes8-20 varied search queries in English and the local language: synonyms, functional descriptions, brand-style names, 'alternatives to X', 'how to X', 'X workaround'.
product_shapeYesWhat the product or way would do or achieve, for whom, through which channel or device. Used to judge closeness.
marketplace_queriesNo3-5 SHORT keyword queries (2-5 words, English) naming the product type as a store listing would, e.g. 'sycophancy ChatGPT extension'. Run inside every app store, launch site, social site and plugin marketplace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), the description discloses execution behavior (queries run in parallel across general web and specific places), the return payload (deduplicated title/URL/snippet/where-found plus a coverage report of queries run and places skipped), and a crucial epistemic caveat that results are unverified and absence is not proof of nonexistence.

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

Conciseness4/5

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

The structure is strong: purpose first, example questions second, execution and return behavior third, parameters last. It is somewhat long and the parameter list repeats schema content, but every block is scannable and nothing is buried.

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 five-parameter, open-world search tool with no output schema, the description covers purpose, place selection, return contents, and limitations thoroughly. The only completeness flaw is the query-count mismatch (4-20 vs 8-20), which slightly muddies the input contract.

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 baseline is 3, and the description's parameter section largely restates the schema's own field descriptions (claim, product_shape, marketplace_queries examples). It also introduces a minor inconsistency, stating "4-20 varied queries" while the schema specifies 8-20, which could confuse an agent about the minimum. The places-to-question-type mapping adds some value but is duplicated in 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 opens with a precise verb and resource set: it searches for things an answer claimed do not exist (products, apps, services, competitors, workarounds, counter-evidence). It distinguishes the resource types it hunts for and the question shapes it serves, so an agent can tell exactly what class of task it addresses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete trigger questions ("is there an app / tool / service that...", "does X exist in my country") and maps question types to specific `places` values, plus an explicit cost/latency tradeoff ("Fewer places is faster and cheaper"). That is actionable when-to-use guidance with no reliance on inference.

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