number7even website check

Fixed price for a finished website check

get_check_quote

Read-only

The fixed price and what it includes for a finished check (s-… from start_website_check, or i-… for a described idea): setup excl. VAT paid 30/40/30, monthly or yearly care, and what is priced in the call. By default for the options we recommend from the check; pass options to price another selection. Applications have no fixed price (agreed after the assessment or a call). Nothing is ordered: the person orders on the check's page.

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": {
      "id": "<id>"
    },
    "name": "get_check_quote"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The check id (s-… or i-…)
`options`	No	Optional option keys to price instead of the recommendation, e.g. ["languages","booking"]. The basics are always included.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces the no-side-effect profile explicitly: 'Nothing is ordered: the person orders on the check's page.' It also discloses behavioral content the annotations cannot, such as the absence of a fixed price for applications and the payment split structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the prose is a dense run-on with parentheticals and domain jargon ('care', '30/40/30') that takes effort to parse. Most sentences carry information, yet the phrasing could be split for readability.

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 two-parameter, read-only tool with no output schema, the description covers what is priced, how ids are formed, the default for options, and the no-ordering guarantee. Only the shape of the returned quote is left implicit, which is acceptable given its simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that options defaults to the recommended selection from the check, that passing options prices an alternative selection, and what the two id prefixes signify.

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 states the specific resource: the fixed price and its composition for a finished website check, and distinguishes the two id origins (s-… from start_website_check, i-… for a described idea). It never uses a clean verb like 'returns the quote', but an agent can tell this apart from get_check_status or get_booking_link.

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?

It implies when the tool applies ('for a finished check') and gives one exclusion ('Applications have no fixed price'), plus default-vs-override guidance for the options argument. It does not name any sibling as an alternative or say what to do when no fixed price exists besides 'assessment or a call'.

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

All number7even website check tools Inspect

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

Need Help?