SAP MCP Server

Check SNS Ownership

sap_sns_check_ownership

Read-onlyIdempotent

Check whether a wallet matches the resolved SNS wallet for a .sol domain. This uses the SOL record when present and the domain owner as fallback.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

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

Input Schema

Name	Required	Description
`owner`	No	Canonical field: Solana public key (base58) of the wallet to verify as the domain owner
`domain`	No	The .sol domain name to check ownership of
`wallet`	No	Alias for owner, accepted for agent ergonomics when the user says wallet.

Output Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 24, 2026

addedInput schema / description

Added value: +"Check SNS Ownership input schema. Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. Use exact field names from this schema; do not guess aliases or include private key material."

Changed2 schema fields changedJul 21, 2026

changedInput schema / properties / owner / description

Previous value: -"The Solana public key (base58) of the wallet to verify as the domain owner"New value: +"Canonical field: Solana public key (base58) of the wallet to verify as the domain owner"

addedInput schema / properties / wallet

Added value: +{
+  "description": "Alias for owner, accepted for agent ergonomics when the user says wallet.",
+  "type": "string"
+}

First observedJul 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the fallback behavior (SOL record first, domain owner as fallback) and clarifies the signer boundary: 'hosted reads/builders never receive keypair bytes.' This provides useful context beyond the structured 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 core description is a concise single sentence. The SAP MCP execution guidance block is somewhat generic and lengthy, but it is well-structured with labeled sections (Pricing, Routing, Signer boundary) and provides relevant operational context for the 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 rich output schema, clear annotations, and a detailed input schema, the description covers the essential purpose and logic. It does not explicitly describe edge cases (e.g., domain not found) but the output schema likely handles that. Overall sufficient for a read-only verification tool.

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% and each parameter is documented (owner, domain, wallet alias). The description does not add additional parameter-level semantics beyond what the schema already provides, so the baseline score of 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?

The description clearly states the tool's specific action: 'Check whether a wallet matches the resolved SNS wallet for a .sol domain.' It includes the resolution logic (SOL record with fallback to domain owner), making it distinct from sibling tools like sap_sns_batch_check_domains or sap_sns_resolve_domain.

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?

No guidance provided on when to use this tool versus alternatives. The SAP MCP execution guidance discusses payment routing and signer boundaries, but does not mention batch alternatives or scenarios where this tool is preferred over others.

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

All SAP MCP Server 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.