Skip to main content
Glama

SITEBORNE Utility Network

by net.siteborne
OverviewDiscussionsAdmin

Get SITEBORNE quote

siteborne_get_quote
Read-onlyIdempotent

Build a canonical x402 payment quote for one SITEBORNE service and exact request input. Use when: an agent needs the governed price, payee, network, asset, resource, expiry, and payment requirement before deciding whether to invoke a paid service. Do not use when: evidence work is required now (use the matching siteborne_build_company_evidence_graph, siteborne_retrieve_verified_web_context, siteborne_extract_document_evidence_json, or siteborne_verify_agent_output tool), or only availability is needed (use siteborne_get_service_health). Parameters: scheme must be the one scheme the service is offered under (company_evidence_graph.v2 exact, web_context_verified.v2 exact, document_evidence_json.v2 upto, verify_agent_output.v2 exact, company_evidence_graph.v3 exact, web_context_verified.v3 exact, document_evidence_json.v3 upto, verify_agent_output.v3 exact); any other scheme is rejected with scheme_not_offered. input is hashed, so the quote binds only that exact request. Behavior: quote-only and read-only; it hashes the proposed input, and does not execute the underlying paid service, verify payment, call a provider, create a Workflow, or settle. Economics: free of charge. The returned amount is the exact price, or for upto an authorized maximum whose actual_amount is null because the real charge is measured at settlement and never exceeds it. Failure: a mode that has a governed price but is unavailable returns retrieval_mode_unavailable or verification_mode_unavailable and no quote; a quote expires at expires_at. Returns: an expiring input-bound quote with its x402 payment requirement and the canonical economics block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesComplete proposed input for the selected service; its canonical hash binds the quote and later payment requirement to this exact request content.
schemeYesPricing mode: exact fixes the required amount, while upto authorizes a maximum whose eventual charge cannot exceed the returned amount.
service_idYesCanonical SITEBORNE service and major version to price; selects that service’s governed pricing key, contract release, and production resource URL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesToken contract address on the network that the amount is denominated in.
payeeYesPublic payTo address that receives the payment.
amountYesAmount in the asset atomic units (6 decimals for USDC): the exact price when amount_kind is exact, or the authorized maximum when it is authorized_maximum.
schemeYesx402 scheme: exact requires the amount; upto authorizes it as a maximum.
networkYesCAIP-2 network the payment must be made on (for example eip155:8453).
quote_idYesDeterministic identifier of this quote.
economicsYesThe canonical economic contract for the quoted service (pricing model, tiers, authorization maximum, settlement model, modes and their availability, limits, production state, pricing_source_version, and network/asset/pay_to); identical on every SITEBORNE discovery surface.
issued_atYesUTC time the quote was issued.
expires_atYesUTC time after which the quote is no longer valid.
input_hashYesCanonical hash of the exact request input this quote binds.
service_idYesCanonical service id and major version that was quoted.
amount_kindYesexact: the charge equals amount. authorized_maximum: the charge is measured at settlement and never exceeds amount.
pricing_keyYesGoverned pricing key the amount was resolved from (governance pricing authority).
resource_idYesCanonical URL of the paid resource this quote is bound to.
binding_hashYesHash binding the quote to the exact service, input hash, price, scheme, network, asset, and payee; a payment for a different binding is not accepted.
actual_amountYesAlways null in a quote: the actual charge exists only after measured settlement.
requirement_idYesIdentifier of the x402 payment requirement embedded in payment_requirements.
service_versionYesService contract major version.
contract_releaseYesContract release the quoted service belongs to.
payment_requiredYesAlways true: executing the quoted service requires payment.
production_enabledYesQuote-level flag, always false: a quote never authorizes execution. The service runtime state is economics.production_enabled.
payment_requirementsYesThe x402 payment requirement to satisfy, including payTo, network, asset and amount.
pricing_source_versionYesVersion of the governed pricing document that produced the amount; a repricing changes this value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / service_id / enum
      Previous value: -[
-  "company_evidence_graph.v1",
-  "web_context_verified.v1",
-  "document_evidence_json.v1",
-  "verify_agent_output.v1",
-  "company_evidence_graph.v2",
-  "web_context_verified.v2",
-  "document_evidence_json.v2",
-  "verify_agent_output.v2"
-]New value: +[
+  "company_evidence_graph.v1",
+  "web_context_verified.v1",
+  "document_evidence_json.v1",
+  "verify_agent_output.v1",
+  "company_evidence_graph.v2",
+  "web_context_verified.v2",
+  "document_evidence_json.v2",
+  "verify_agent_output.v2",
+  "company_evidence_graph.v3",
+  "web_context_verified.v3",
+  "document_evidence_json.v3",
+  "verify_agent_output.v3"
+]
    • changedOutput schema / properties / contract_release / enum
      Previous value: -[
-  "1.0.0",
-  "2.0.0"
-]New value: +[
+  "1.0.0",
+  "2.0.0",
+  "3.0.0"
+]
    • changedOutput schema / properties / service_version / enum
      Previous value: -[
-  "v1",
-  "v2"
-]New value: +[
+  "v1",
+  "v2",
+  "v3"
+]
  2. Changed24 schema fields changed
    • addedOutput schema / properties / actual_amount / description
      Added value: +"Always null in a quote: the actual charge exists only after measured settlement."
    • addedOutput schema / properties / amount / description
      Added value: +"Amount in the asset atomic units (6 decimals for USDC): the exact price when amount_kind is exact, or the authorized maximum when it is authorized_maximum."
    • addedOutput schema / properties / amount_kind / description
      Added value: +"exact: the charge equals amount. authorized_maximum: the charge is measured at settlement and never exceeds amount."
    • addedOutput schema / properties / asset / description
      Added value: +"Token contract address on the network that the amount is denominated in."
    • addedOutput schema / properties / binding_hash / description
      Added value: +"Hash binding the quote to the exact service, input hash, price, scheme, network, asset, and payee; a payment for a different binding is not accepted."
    • addedOutput schema / properties / contract_release / description
      Added value: +"Contract release the quoted service belongs to."
    • addedOutput schema / properties / economics
      Added value: +{
+  "additionalProperties": {},
+  "description": "The canonical economic contract for the quoted service (pricing model, tiers, authorization maximum, settlement model, modes and their availability, limits, production state, pricing_source_version, and network/asset/pay_to); identical on every SITEBORNE discovery surface.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / expires_at / description
      Added value: +"UTC time after which the quote is no longer valid."
    • addedOutput schema / properties / input_hash / description
      Added value: +"Canonical hash of the exact request input this quote binds."
    • addedOutput schema / properties / issued_at / description
      Added value: +"UTC time the quote was issued."
    • addedOutput schema / properties / network / description
      Added value: +"CAIP-2 network the payment must be made on (for example eip155:8453)."
    • addedOutput schema / properties / payee / description
      Added value: +"Public payTo address that receives the payment."
    • addedOutput schema / properties / payment_required / description
      Added value: +"Always true: executing the quoted service requires payment."
    • addedOutput schema / properties / payment_requirements / description
      Added value: +"The x402 payment requirement to satisfy, including payTo, network, asset and amount."
    • addedOutput schema / properties / pricing_key / description
      Added value: +"Governed pricing key the amount was resolved from (governance pricing authority)."
    • addedOutput schema / properties / pricing_source_version / description
      Added value: +"Version of the governed pricing document that produced the amount; a repricing changes this value."
    • addedOutput schema / properties / production_enabled / description
      Added value: +"Quote-level flag, always false: a quote never authorizes execution. The service runtime state is economics.production_enabled."
    • addedOutput schema / properties / quote_id / description
      Added value: +"Deterministic identifier of this quote."
    • addedOutput schema / properties / requirement_id / description
      Added value: +"Identifier of the x402 payment requirement embedded in payment_requirements."
    • addedOutput schema / properties / resource_id / description
      Added value: +"Canonical URL of the paid resource this quote is bound to."
    • addedOutput schema / properties / scheme / description
      Added value: +"x402 scheme: exact requires the amount; upto authorizes it as a maximum."
    • addedOutput schema / properties / service_id / description
      Added value: +"Canonical service id and major version that was quoted."
    • addedOutput schema / properties / service_version / description
      Added value: +"Service contract major version."
    • changedOutput schema / required
      Previous value: -[
-  "quote_id",
-  "binding_hash",
-  "service_id",
-  "service_version",
-  "contract_release",
-  "input_hash",
-  "pricing_key",
-  "pricing_source_version",
-  "scheme",
-  "network",
-  "asset",
-  "amount",
-  "amount_kind",
-  "actual_amount",
-  "resource_id",
-  "requirement_id",
-  "payment_requirements",
-  "payee",
-  "issued_at",
-  "expires_at",
-  "production_enabled",
-  "payment_required"
-]New value: +[
+  "quote_id",
+  "binding_hash",
+  "service_id",
+  "service_version",
+  "contract_release",
+  "input_hash",
+  "pricing_key",
+  "pricing_source_version",
+  "scheme",
+  "network",
+  "asset",
+  "amount",
+  "amount_kind",
+  "actual_amount",
+  "resource_id",
+  "requirement_id",
+  "payment_requirements",
+  "payee",
+  "issued_at",
+  "expires_at",
+  "production_enabled",
+  "payment_required",
+  "economics"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / input / description
      Added value: +"Complete proposed input for the selected service; its canonical hash binds the quote and later payment requirement to this exact request content."
    • addedInput schema / properties / scheme / description
      Added value: +"Pricing mode: exact fixes the required amount, while upto authorizes a maximum whose eventual charge cannot exceed the returned amount."
    • addedInput schema / properties / service_id / description
      Added value: +"Canonical SITEBORNE service and major version to price; selects that service’s governed pricing key, contract release, and production resource URL."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive behavior, and the description adds substantial specifics: it hashes input, does not execute the paid service, verify payment, call a provider, create a Workflow, or settle; it is free; failures return mode-unavailable errors and no quote; quotes expire at expires_at. There is no contradiction with 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Despite being long, the description is organized into labeled blocks and every sentence adds a distinct decision-relevant fact: purpose, routing, parameter constraints, non-execution behavior, economics, failure, and return shape. There is no filler or tautology.

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 three required parameters, enums, an output schema, and a complex sibling set, the description covers selection criteria, parameter constraints, behavior, failure modes, and return shape. An agent has enough to invoke correctly and interpret a non-error result.

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?

With 100% schema coverage, the baseline is 3, but the description adds the cross-parameter invariant that scheme must be the scheme the selected service is offered under, enumerates the service-to-scheme mapping, and warns of scheme_not_offered rejection. It also explains that input is hashed so the quote binds exact content. This lifts it above baseline, though the mapping omits the v1 service_id variants that exist in the schema enum.

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: 'Build a canonical x402 payment quote for one SITEBORNE service and exact request input.' It also ties the purpose to deciding whether to invoke a paid service, which distinguishes this quote-only tool from the evidence-building siblings by intent, not just name.

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' sections name the exact sibling tools for evidence work and health checks, plus the condition that selects the quote tool. This is the clearest possible routing guidance; nothing is left 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