Skip to main content
Glama

Company Finders

Check one website

check_website
Read-only

Visits one website now and reports whether it loads, is broken or looks out of date, with the reason. Costs 1 credit ($0.003).

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website address, for example example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds value the annotations do not: the cost (1 credit / $0.003), the fact that it performs a live visit, and the shape of the verdict (loads / broken / out of date, with reason). It does not mention latency or failure modes such as timeouts.

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?

Two short sentences, front-loaded with the action and result, then the cost. Nothing is wasted and the credit price is genuinely decision-relevant information for an agent.

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?

For a one-parameter read-only tool with no output schema, the description covers the action, the returned verdict, and the cost. The only minor gap is that 'looks out of date' is left undefined and no failure/timeout behavior is described.

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 only one parameter and schema coverage is 100%, with the schema itself providing an example ('example.com') and length bounds. The description adds no format guidance (e.g. scheme optional, no paths) beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Visits one website now') and states what it returns: load status plus a reason. The word 'one' scopes it to a single site, which implicitly separates it from bulk operations, though no sibling is named and the listed siblings (build_list, get_balance, etc.) belong to a different domain.

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?

'now' conveys that this is a live, on-demand check rather than a cached or scheduled one, which is useful usage context. However, there is no explicit when-to-use, when-not-to-use, or alternative tool named, so the agent must infer that this is for individual-site validation.

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