Skip to main content
Glama
Sign In
@gridwork/siteaudit

@gridwork/siteaudit

by thegridwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

quick_check

Quickly assess a site's health with scores and grades. Fast triage for URLs without delving into detailed issues.

Instructions

Get a quick overview of a site's health — scores and grades only, no detailed issues. Fast way to triage a URL.

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": {
      "url": "<url>"
    },
    "name": "quick_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

The description notes that the tool returns 'scores and grades only, no detailed issues,' which sets expectations about output scope. With no annotations provided, the description bears full burden and could mention error handling or required authentication.

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 two sentences with no wasted words, immediately conveying the core functionality and use case.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides sufficient context about what it does and returns. It could be slightly more explicit about the structure of scores/grades.

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?

The schema covers 100% of the parameter ('url'), and the description adds minimal additional context beyond the schema's own description. The phrase 'URL to check' is straightforward, so the description doesn't significantly enhance understanding.

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 clearly states the tool provides a quick site health overview with scores and grades only, distinguishing it from more detailed sibling tools like audit_site or audit_seo.

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 describes the tool as a 'fast way to triage a URL,' implying it's for quick initial checks rather than detailed analysis. However, it does not explicitly mention when not to use or name specific alternatives.

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

Deploy Server

Other Tools