Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Payment provider detect

web-technology_payment-provider-detect
Read-onlyIdempotent

Detect payment processors and checkout widgets from the Payment processors technology category. Price $0.03 USDC. POST /api/v1/web-technology/payment-provider-detect. An unpaid call returns the x402 payment terms and does not run.

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": "web-technology_payment-provider-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNourl, string, length 0 to 2000. Optional.
htmlNohtml, string, length 0 to 2097152. Optional.
metaNometa, object. Optional.
cookiesNocookies, array. Optional.
headersNoheaders, object. Optional.
scriptUrlsNoscriptUrls, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
providersNoproviders. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful non-schema context: price, POST endpoint, and that unpaid calls return x402 payment terms without running. This is useful payment/auth behavior beyond annotations, though it does not discuss rate limits or output shape because an output schema exists.

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 three compact sentences and front-loads the purpose, then the payment requirement and endpoint. Price, endpoint, and unpaid-call terms earn their place for a paid x402 tool, though 'from the Payment processors technology category' is slightly redundant with the stated purpose.

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 paid detection tool with six optional inputs, four annotations, and an output schema, the description covers the critical operational fact that unpaid calls do not execute. It does not explain how inputs should be combined, but the input schema documents those inputs and the output schema covers return values. Adequate overall.

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 the schema already documents all six optional parameters and nested cookie fields. The description adds no parameter-specific meaning such as how url vs html vs scriptUrls are used. Baseline 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 states a specific detection verb and names payment processors and checkout widgets, scoped to the Payment processors technology category, which differentiates it from broader siblings such as technology-detect. It stops short of explicitly naming an alternative tool or routing condition, so it is clear but not fully sibling-differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternative sibling tools. The purpose implies detecting payment providers on a page, but an agent gets no explicit selection criteria or exclusions.

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