Skip to main content
Glama

Check Wikipedia notability, source by source

check_wikipedia_notability
Read-onlyIdempotent

Free and read-only. Tests a subject’s sources against Wikipedia’s notability guidelines (WP:GNG, WP:NCORP, WP:BASIC, WP:CREATIVE), the same verdicts as the free checker on essentras.com. Ask the person what the article would be about, their connection to it, and for each source its type and 5 yes, no or unsure answers (never the outlet, headline, link or the person’s name). Returns a verdict per source (counts, supports facts only, does not count, unclear, counts once) with the Wikipedia rule, its link and the date it was read, an overall band, disclosure duties for a conflict of interest or paid editing, and the Essentras service with its current price only when the band is "Reviewer judgment applies". Press releases, sponsored articles and paid placements, Essentras placements included, never count toward notability. The bands are an Essentras rule of thumb, and volunteer reviewers decide.

Input Schema

NameRequiredDescriptionDefault
sourcesNoYour sources, up to 25. Start with your strongest. Each source is judged on its own, then the list is judged as a whole. Give each source its type and, for the types that can count, the answers to the 5 questions (yes, no or unsure). Never send the outlet, headline or link: the type and the answers decide the verdict.
subjectYesWhat is the article about? person = A person (WP:BASIC); org = A company or organization (WP:NCORP); creative = An author, artist, journalist or other creative professional (WP:CREATIVE); other = Something else (an event, book, film, website or product) (WP:GNG).
criteriaNoPeople and creative professionals only. Does any of these apply? Alternative routes for people (WP:ANYBIO): nbio:0 = A well-known and significant award or honor, or several nominations for one; nbio:1 = A widely recognized contribution that is part of the enduring historical record in their field; nbio:2 = An entry in a country’s standard national biographical dictionary. Creative professional criteria (WP:CREATIVE): creative:0 = Regarded as an important figure, or widely cited by peers or successors; creative:1 = Known for originating a significant new concept, theory or technique; creative:2 = Created a significant or well-known work that has been the primary subject of multiple independent articles or reviews; creative:3 = Work that became a significant monument, was a substantial part of a significant exhibition, won significant critical attention, or is held in the permanent collections of several notable galleries or museums.
connectionNoWhat is your connection to it? none = No connection; coi = It is me, my employer or someone close to me; paid = I am paid or rewarded to work on it; client = I am hiring someone to do it.none
single_eventNoPeople and creative professionals only. Is almost all of the coverage about a single event?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint=false, idempotentHint, destructiveHint=false), yet the description adds substantial context: the per-source verdict vocabulary, the returned rule citation with link and read date, conditional disclosure duties, and a price surfaced only when the band is 'Reviewer judgment applies'. It also states a substantive rule (press releases, sponsored and paid placements never count) and a limitation disclaimer that the bands are an Essentras rule of thumb while volunteer reviewers decide.

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 opening 'Free and read-only' front-loads the key constraint, and the middle sentences about the input-gathering protocol and return shape earn their place. It is dense and slightly run-on in the return-value and press-release clauses, and the 'never send the outlet, headline or link' instruction duplicates schema text, costing a point.

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

Completeness5/5

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

With no output schema, the description carries the full burden of explaining returns and does so thoroughly: per-source verdicts, overall band, rule citation with link and date, disclosure duties, and the conditional service/price mention. Inputs, output shape, and scope limits are all covered, so an agent needs nothing further to invoke and interpret it.

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%, and the enum descriptions for source type, the five questions, subject, criteria and connection are unusually detailed, so the schema does the heavy lifting. The description repeats the data-minimization rule ('never the outlet, headline, link or the person's name') that the schema's sources description already states, adding no new parameter meaning. Baseline 3 applies.

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 names a specific action (tests a subject's sources against Wikipedia notability guidelines) and enumerates the exact rules applied (WP:GNG, WP:NCORP, WP:BASIC, WP:CREATIVE). It is clearly distinguishable from sibling checks like check_knowledge_panel_readiness or check_review_removability, which address different platforms entirely.

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?

It gives concrete procedural guidance: ask about the article subject, the person's connection, and each source's type plus five yes/no/unsure answers, with an explicit exclusion list of data never to submit. What it lacks is any statement of when NOT to use this tool or which sibling to prefer for adjacent questions, so it stops short of a full 5.

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.