Skip to main content
Glama

Check whether the site already covers a topic

check_site_coverage
Read-onlyIdempotent

Checks the latest crawl of a Hi, Moose project for pages that already cover one or more topics. For each topic it answers covered, partial, uncovered or unknown, with up to five of the closest pages (URL, title and similarity score, the pages the verdict rests on marked as evidence) and the date of the crawl it checked. Use it when the user asks whether their site already has something, and before proposing new content. unknown means the check could not run for that topic, not that the site lacks it; the row gives the reason. For the full list of pages on a topic, use find_site_pages.

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": {
      "project": "<project>",
      "topics": "<topics>"
    },
    "name": "check_site_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicsYesOne to fifteen topics, each a short phrase such as "SBOM generation for Python" or "SCA vs SAST".
projectYesThe Hi, Moose project, by its name as shown by list_projects.
parentTopicNoOptional wider subject the topics belong to, used to judge partial coverage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description goes further by disclosing the return shape (verdict per topic, up to five closest pages with URL, title and similarity score, evidence marking, crawl date). It also flags a genuine failure mode: 'unknown means the check could not run for that topic, not that the site lacks it; the row gives the reason' — a semantic distinction an agent would otherwise misread as negative coverage.

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?

Three sentences, front-loaded with purpose, then return shape, then the unknown caveat, then the sibling pointer. Every sentence carries distinct information and none is redundant with the title or schema.

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 available, the description supplies the return contract itself — verdict vocabulary, page evidence fields, and crawl date — plus the unknown-state caveat. That is everything an agent needs to call this correctly and interpret the result, matching the tool's moderate complexity.

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 all three parameters including parentTopic and the 1-15 topic limit are already documented in the schema. The description restates 'one or more topics' and adds no syntax, format or constraint details beyond that, so it sits at the baseline where the schema does the work.

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?

States a specific verb and resource: 'Checks the latest crawl of a Hi, Moose project for pages that already cover one or more topics.' It also distinguishes itself from the sibling find_site_pages by scoping that tool to the full page list, so an agent can pick between the two without opening either schema.

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?

Explicit when-to-use is given: 'when the user asks whether their site already has something, and before proposing new content.' An alternative is named with the condition that selects it ('For the full list of pages on a topic, use find_site_pages'), leaving nothing to 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