Skip to main content
Glama

MCP x402 - Evidence-Backed Web Verification

Verify conditions with evidence

verificar_condicoes
Read-only

Use before an agent trusts, buys or acts to test 1 to 10 explicit conditions against one public HTTP or HTTPS page. Best fits offer and warranty checks, seller identity or authorization checks, and policy compliance checks. Returns confirmed, rejected or uncertain for every condition with textual evidence when available, plus source, verifiedAt, verificationId and pageHash. Missing evidence produces uncertain, not a false confirmation. Use preview_verification first when the buyer needs a free example. PT: Verifica condições com prova auditável.

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>",
      "condicoes": "<condicoes>"
    },
    "name": "verificar_condicoes"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL HTTP ou HTTPS pública onde as condições serão verificadas. Endereços locais, privados e não públicos são rejeitados.
contextoNoContexto opcional, até 500 caracteres, usado apenas para interpretar as condições e nunca como prova da página.
condicoesYesLista de 1 a 10 condições concretas e verificáveis; cada condição deve ter entre 3 e 300 caracteres.

Output Schema

NameRequiredDescriptionDefault
titleYes
sourceYes
decisaoYes
pageHashYes
verifiedAtYes
verificationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "decisao": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "condicoes": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "condicao": {
      +                "type": "string"
      +              },
      +              "estado": {
      +                "enum": [
      +                  "confirmada",
      +                  "rejeitada",
      +                  "incerta"
      +                ],
      +                "type": "string"
      +              },
      +              "explicacao": {
      +                "type": "string"
      +              },
      +              "prova": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "required": [
      +              "condicao",
      +              "estado",
      +              "prova",
      +              "explicacao"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "decisao": {
      +          "enum": [
      +            "confirmado",
      +            "rejeitado",
      +            "incerto"
      +          ],
      +          "type": "string"
      +        },
      +        "resumo": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "decisao",
      +        "condicoes",
      +        "resumo"
      +      ],
      +      "type": "object"
      +    },
      +    "pageHash": {
      +      "pattern": "^sha256:[a-f0-9]{64}$",
      +      "type": "string"
      +    },
      +    "source": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "verificationId": {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    },
      +    "verifiedAt": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "title",
      +    "verifiedAt",
      +    "decisao",
      +    "verificationId",
      +    "pageHash"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / condicoes / description
      Previous value: -"Condições concretas que a página tem de cumprir"New value: +"Lista de 1 a 10 condições concretas e verificáveis; cada condição deve ter entre 3 e 300 caracteres."
    • changedInput schema / properties / contexto / description
      Previous value: -"Contexto opcional para interpretar as condições"New value: +"Contexto opcional, até 500 caracteres, usado apenas para interpretar as condições e nunca como prova da página."
    • changedInput schema / properties / url / description
      Previous value: -"URL público HTTP ou HTTPS"New value: +"URL HTTP ou HTTPS pública onde as condições serão verificadas. Endereços locais, privados e não públicos são rejeitados."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly/openWorld/non-destructive, but the description adds real value beyond them: trichotomous outcomes, evidence attachment, and the crucial failure policy 'missing evidence produces uncertain, not a false confirmation'. It doesn't mention rate limits, cost, or latency, which keeps it from a 5.

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?

Front-loaded with purpose and trigger, then use cases, then return shape, then fallback. The trailing 'PT: Verifica condições com prova auditável' is a redundant echo of the title and does no work 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?

With a full output schema already present, the description needn't enumerate fields, and it still names the outcome vocabulary and the conservative-failure rule. Adequate for a read-only, 3-parameter tool; only the absence of any note on cost, latency or page-access failure modes leaves a small gap.

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%, so url, condicoes and contexto are already documented with limits and rejection rules. The description restates the 1-to-10 condition bound but adds nothing about the 'contexto' parameter's non-evidentiary role, so baseline 3 applies.

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?

States a specific verb and resource with precise scope: test 1 to 10 explicit conditions against one public HTTP/HTTPS page, before an agent 'trusts, buys or acts'. Clearly distinguishable from consultar_ia (generic) and preview_verification (free example), which it names as a different mode.

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?

Explicit trigger ('before an agent trusts, buys or acts') plus named ideal use cases (offer/warranty, seller identity/authorization, policy compliance). It also routes to a sibling: 'Use preview_verification first when the buyer needs a free example.'

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.