Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Find broken internal links

validate_links
Read-onlyIdempotent

Scan every page and block of one design for internal links that point at a page the site does not have, with the page each one is on and its line. Dynamic links (e.g. to each blog post) are counted but not judged; external links are not fetched. variation_id picks the design (from list_variations); omit it for the site's chosen design. Changes nothing — fix a broken link with refine_site or add the missing page.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
variation_idNoThe design to scan, from list_variations. Omit for the site's chosen design.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, and non-destructive, so the description does not need to re-prove safety. It does add useful scope details: dynamic links are counted but not judged, external links are not fetched, and the output includes the page and line for each broken link.

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?

The description is tight and front-loaded: it leads with the scan scope, then the result shape, then edge cases, then variation selection, then remediation alternatives. Each sentence carries operational information.

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?

There is no output schema, so the description must explain the return value, and it does: the page each broken link is on and its line. It also covers excluded link types and remediation paths, making it complete enough for an agent to call correctly.

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 parameters are fully documented in the schema. The description restates variation_id's meaning and omission behavior but does not add syntax or constraints beyond what the schema already says; site_id and user_goal are not discussed.

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 verb and resource: scanning one design's pages and blocks for internal links to pages the site does not have, returning the offending page and line. This clearly separates it from validate_design, which checks design validity rather than link targets.

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 states when to use it (find broken internal links) and gives the exact alternative for remediation: refine_site to fix a link or add_page for the missing target. It also tells the caller to pick variation_id from list_variations or omit it for the chosen design.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources