Skip to main content
Glama

mocop

analyze_site

Read-only

Score how agent-ready a website is (0-10) with per-area checks and recommendations.

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": "analyze_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the result includes per-area checks and recommendations, which helps an agent plan follow-up work. It does not disclose whether the target site must be registered/verified, whether the call is slow or rate-limited, or how the 0-10 score is derived — a real gap for a tool that presumably fetches external content despite openWorldHint=false.

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?

One tight sentence with the action verb front-loaded and zero waste. Brevity is appropriate for a single-parameter read tool, though a short clause on input format or prerequisites would have been worth the extra words.

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

Completeness3/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 a decent job sketching the return (score plus per-area checks and recommendations), but it omits input format and preconditions. For a read-only, single-parameter tool this is adequate rather than complete.

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?

There is a single required parameter with 0% schema description coverage, so the description must carry the semantics. It only says "a website", leaving format ambiguous (bare domain vs full URL) and not stating whether the domain must already exist in the account. It identifies the parameter's meaning but adds no usable syntax guidance.

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 pairs a specific verb ("Score") with a specific resource ("how agent-ready a website is") and adds the output shape (0-10 scale, per-area checks, recommendations). It is clearly distinguishable from read-oriented siblings such as get_guide or verify_domain, though it never names an alternative explicitly.

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 only implied: an agent can infer it should call this when it wants an agent-readiness assessment of a site. There is no statement of prerequisites (must the domain be added or verified first?), no cost/latency expectations, and no exclusion against siblings like verify_domain or domain_dns_guide.

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