Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Internal links: report or one page's link graph

webops_links
Read-onlyIdempotent

The website's internal links from the latest crawl: per page links in and out, issues (broken, redirecting, noindex or nofollow targets, generic or off-topic words, the same words for two pages), click depth and suggested links; or one page's link graph. Coverage says how much of the site the crawl read; depth and orphans are judged only when it read all. Another organization's or an unconnected site answers not found. Read-only.

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": {
      "domain": "<domain>"
    },
    "name": "webops_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne page: its links in and out with their words, issues and suggested links.
domainYes
path_prefixNoOnly pages under this path in the report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world, so the bar is lower, yet the description adds real behavioral facts: depth and orphan judgments only apply to a full-coverage crawl, and another organization's or unconnected site returns not found. It also enumerates the issue classes reported. It stops short of rate limits or response shape details, but the added context is substantial.

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?

Content is front-loaded with the resource and its two modes, then the caveats. It is dense — a long semicolon-chained sentence — but nearly every clause carries information an agent needs; the enumerated issue list is the only part bordering on over-detail.

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?

With no output schema, the description does the work of listing what comes back (links in and out, issues, click depth, suggested links, coverage). It also flags the partial-crawl caveat and the not-found case. Missing only explicit routing guidance against sibling tools.

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 67%, and the schema already describes page and path_prefix. The description restates 'one page's link graph' and the path filtering without adding format or edge-case detail, and the required domain parameter gets no explanation beyond the not-found note. Adequate but adds little beyond the schema.

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 states the resource precisely ('the website's internal links from the latest crawl') and distinguishes its two modes: a site-wide report versus 'one page's link graph'. It never names a sibling tool, so an agent must still infer how this differs from webops_pages or webops_page_dossier.

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?

Usage is implied rather than stated: supplying page switches to single-page mode, path_prefix narrows the report. There is no explicit 'use this when... / use X instead' guidance relative to the many sibling tools that likely also surface link or page data.

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