MCP x402 - Evidence-Backed Web Verification

Analyze a public web page

analisar_url

Read-only

Use to fetch one public HTTP or HTTPS page and return a source-bounded report with summary, facts, risks and recommended actions. The optional objective controls focus but is never evidence. It does not consult other sources; use verificar_condicoes for condition-by-condition decisions. PT: Analisa uma página pública sem usar fontes externas.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	URL HTTP ou HTTPS pública a extrair. Endereços locais, privados e não públicos são rejeitados.
`objetivo`	No	Foco opcional do relatório, até 500 caracteres; orienta a análise mas não é tratado como prova.

Output Schema

Name	Required	Description	Default
`title`	Yes
`report`	Yes
`source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "report": {
+      "type": "string"
+    },
+    "source": {
+      "format": "uri",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "title",
+    "report"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / objetivo / description

Previous value: -"Objetivo opcional da análise"New value: +"Foco opcional do relatório, até 500 caracteres; orienta a análise mas não é tratado como prova."

changedInput schema / properties / url / description

Previous value: -"URL público HTTP ou HTTPS"New value: +"URL HTTP ou HTTPS pública a extrair. Endereços locais, privados e não públicos são rejeitados."

First observedAug 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: single-source bounded analysis, no external sources, and the objective is not evidence. It does not cover edge cases like non-HTML pages or failure behavior, but the annotation coverage lowers the burden.

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 and efficient, stating purpose and scope in the first sentence. The PT translation adds length but is a reasonable bilingual aid; no sentence is extraneous.

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?

Given an output schema and annotations covering safety and open-world behavior, the description supplies the key remaining context: single-page scope, no external sources, and sibling routing. Minor gaps around failure modes or content-type limitations keep it from being fully exhaustive.

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 description coverage is 100%, so both url and objetivo are already documented in the schema. The description reinforces that objetivo controls focus but is never evidence, but this largely repeats the schema description rather than adding new syntax, constraints, or examples.

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 states a specific verb and resource: fetch one public HTTP/HTTPS page and return a report with summary, facts, risks, and recommended actions. It also distinguishes the tool from sibling verificar_condicoes by saying it does not consult other sources and by naming the alternative for condition-by-condition decisions.

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 explicitly says when to use this tool (one public page), what it does not do (consult other sources), and which sibling to use instead for condition-by-condition decisions. The optional objective is also framed as focus-only, not evidence.

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

All MCP x402 - Evidence-Backed Web Verification 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.