Skip to main content
Glama

Score a website on The Standard

score_website
Read-onlyIdempotent

Score any public website out of 10 on The Standard: secure, works on phones, fast, Google-ready, structured data, readable by AI, answers visitors, books online, has an AI door, shares well.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website address, e.g. example.com

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful context by disclosing the scoring scale and the exact criteria evaluated, plus the public-only constraint. It does not describe cost, latency, or what the result actually looks like, which is the remaining behavioral gap.

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?

A single front-loaded sentence with the verb, scale, and criteria in order of importance. The ten-item criteria list is long but each item is informative and none is padding; it could be trimmed slightly but nothing is redundant.

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?

For a read-only scoring tool with no output schema, the description explains what is evaluated but never hints at the return shape — a single number, a per-criterion breakdown, or prose. That omission matters because the agent cannot otherwise predict the response. Everything else needed to invoke the tool is present.

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% and the single 'url' parameter already carries an example, so the schema does the heavy lifting. The description only adds the qualifier 'public website', which marginally narrows what URLs are acceptable; it adds no format or validation detail 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?

States a specific verb and resource (score a website), the scale (out of 10), and enumerates the ten criteria that make up 'The Standard'. The phrase 'The Standard' is branded jargon that is only inferable from the criteria list, and no sibling differentiation is offered, but the enumerated dimensions make the operation unambiguous.

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?

'Score any public website' implies the usage scope and quietly excludes non-public/internal sites, which is useful. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no statement about whether the site must be reachable or what happens on failure.

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