Skip to main content
Glama

SITEBORNE Utility Network

by net.siteborne
OverviewDiscussionsAdmin

Retrieve verified web context

siteborne_retrieve_verified_web_context
Idempotent

Retrieve and verify evidence from one public web URL using direct HTTP retrieval. Use when: the request is specifically about the content and provenance of a URL. Do not use when: evidence must be synthesized for a company (use siteborne_build_company_evidence_graph), extracted from an authorized document (use siteborne_extract_document_evidence_json), checked against an existing output contract (use siteborne_verify_agent_output), or the page requires JavaScript rendering (rendered retrieval is not available). Parameters: retrieval_mode must be direct; rendered is defined but unavailable and is rejected before any payment challenge, never substituted with direct retrieval. output_mode structured needs buyer_schema and field_selectors to be meaningful; redirect_policy and max_redirects bound redirect following; max_content_size bounds returned bytes; maximum_authorized_price only constrains payment and never changes retrieval scope. Behavior: open-world: a paid request performs bounded outbound HTTP retrieval of the target URL through a safe-egress boundary (private and loopback destinations are refused) and persists governed payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. Retrieval admission follows the governed runtime rate policy; no fixed public per-origin rate is promised. This service is currently production-disabled and rejects execution. Economics: exact price of $0.008 USD per request in direct mode; the payment challenge requires that amount and the charge settles at exactly that amount. rendered mode has a governed price of $0.029 USD but is not available: it is rejected before any payment challenge and never substituted. Failure: schema-invalid input and unavailable modes are rejected before any payment challenge; target-site errors, timeouts and unavailable retrieval return a structured MCP error and are never answered with a substitute result. Returns: normalized, source-attributed web context with verification and PCC evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_urlYesPublic HTTP or HTTPS URL to retrieve and verify; private, loopback, and otherwise unsafe network destinations are rejected.
locale_hintNoOptional BCP 47 language or language-region hint used for HTTP content negotiation; it does not translate content.
output_modeNoResult representation: clean_text normalizes prose, markdown preserves document structure, and structured validates selected fields against buyer_schema.clean_text
buyer_schemaNoOptional JSON Schema governing structured output; meaningful only with output_mode structured and bounded to fifty properties and depth five.
max_redirectsNoMaximum redirect hops from 0 through 10 when the selected redirect policy follows redirects.
retrieval_modeYesRetrieval mode. Only direct (plain HTTP retrieval, no JavaScript execution) is available. rendered has a governed price but is not available: it is rejected with retrieval_mode_unavailable before any payment challenge and is never substituted with direct retrieval.
field_selectorsNoUp to thirty requested field names for structured extraction; narrows the structured result rather than changing the fetched URL.
redirect_policyNoRedirect handling: follow permits the bounded chain, follow_first permits only the first hop, and manual returns redirect evidence without following.follow
max_content_sizeNoMaximum returned content size in bytes, from 1,024 through 10,485,760; smaller limits truncate or reject oversized content sooner.
freshness_secondsNoMaximum acceptable cached-content age in seconds, from 0 through 2,592,000; zero requests uncached content.
maximum_authorized_priceNoBuyer’s decimal-safe maximum authorized price; constrains the payment requirement and never changes retrieval scope.
minimum_verification_scoreNoRequired PCC verification ratio from 0 through 1; raising it makes evidence acceptance stricter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesOutput schema for web_context_verified.v1 service. Must be a valid PCC 1.0.0 document with required net.siteborne.web-context.v1 extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond the annotations, disclosing exact pricing ($0.008 USD), payment challenge behavior, replay protection, safe-egress boundaries, refusal of private/loopback destinations, production-disabled status, and the guarantee that rendered mode is rejected before payment and never substituted. These are material behavioral traits an agent needs to know, and none contradict the annotations.

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 long but densely organized into purpose, usage, parameters, behavior, economics, failure, and returns sections, which earns its length given the tool's complexity. However, the point that rendered mode is unavailable and never substituted is repeated three times, which is slightly redundant and could be tightened without losing meaning.

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?

For a 12-parameter, payment-gated, production-disabled tool, the description covers every area an agent needs: when to use it, how parameters interact, exact costs, failure semantics, and return shape. The presence of an output schema means detailed return documentation is unnecessary, so nothing critical is missing.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds crucial meaning beyond the schema: it clarifies that retrieval_mode must be direct, that structured output requires buyer_schema and field_selectors, that maximum_authorized_price only constrains payment and never changes retrieval scope, and that max_content_size bounds returned bytes. This resolves ambiguities that the raw schema leaves open.

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 opens with a specific verb and resource: 'Retrieve and verify evidence from one public web URL using direct HTTP retrieval.' It clearly distinguishes this tool from siblings by naming alternative tools and the conditions under which they should be used instead, leaving no ambiguity about what this tool does.

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 'Use when' and 'Do not use when' guidance names three sibling tools with the exact scenarios that should route to them, and also excludes JavaScript-rendered pages. This gives an agent concrete decision criteria rather than leaving usage to inference.

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

All SITEBORNE Utility Network toolsInspect
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