Skip to main content
Glama

Priorivo: Technical SEO & Website Audit for AI Agents

Priorivo Website Check — Free Information

website_check_info
Read-onlyIdempotent

Free read-only information before ordering Priorivo: published EUR 9.90 price for ONE agent Website Check, scan limits, languages, payment choices, developer guide and free website scan or no-payment n8n preview. No account, URL, secret key, payment, order, website scan or private data is required. Call this tool first to decide whether a paid website_check is appropriate; never describe the free preview as a real website audit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "website_check_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYes
currencyYes
paid_toolYes
scan_limitsNo
amount_minorYes
purchase_fitNo
scan_startedYes
developer_urlYes
free_scan_urlYes
order_createdYes
payment_routesNo
n8n_preview_urlYes
payment_operationYes
price_is_live_quoteNo
supported_result_localesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / purchase_fit
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "free_best_for": {
      +      "type": "string"
      +    },
      +    "paid_best_for": {
      +      "type": "string"
      +    },
      +    "paid_result_field": {
      +      "const": "analysis.decision_handoff",
      +      "type": "string"
      +    },
      +    "same_scan_limits": {
      +      "const": true,
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "free_best_for",
      +    "paid_best_for",
      +    "same_scan_limits",
      +    "paid_result_field"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond that by stating no account, URL, secret key, payment, order, website scan, or private data is required, and by clarifying that the free preview should not be treated as a real audit.

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?

The description is front-loaded with the tool's purpose and is generally efficient. The first sentence is dense with product and pricing details, and the phrase about a free website scan or no-payment n8n preview is slightly ambiguous, but overall the structure supports quick tool selection.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the zero-parameter schema, rich annotations, and presence of an output schema, the description provides everything needed to select and invoke the tool correctly. It explains the information covered, the prerequisites, and how the tool relates to the paid website_check alternative.

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?

This tool takes zero parameters, so there is no parameter semantics burden beyond confirming that no inputs are needed. The description reinforces that no account, URL, key, or payment is required, which is useful but largely redundant with the empty schema.

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 that this is a free, read-only information tool for Priorivo Website Check details, enumerating pricing, scan limits, languages, payment choices, developer guide, and preview information. It explicitly distinguishes itself from the paid website_check tool, so an agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives direct guidance: call this tool first to decide whether a paid website_check is appropriate. It also adds a clear usage caveat against describing the free preview as a real website audit, which helps prevent incorrect downstream behavior.

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