SAP MCP Server

Das Search Assets

das_searchAssets

Read-onlyIdempotent

Search NFTs/assets with flexible filters via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.

SAP MCP execution guidance: Intent: read/discovery 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.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page pagination control for Das Search Assets.
`burnt`	No	Burnt parameter for Das Search Assets.
`limit`	No	Limit controlling the maximum number of results returned by Das Search Assets.
`frozen`	No	Frozen parameter for Das Search Assets.
`jsonUri`	No	Json URI parameter for Das Search Assets.
`grouping`	No	Grouping key-value pair (e.g. ["collection", "mint_address"])
`compressed`	No	Compressed parameter for Das Search Assets.
`ownerAddress`	No	Solana public key (base58)
`creatorAddress`	No	Solana public key (base58)

Output Schema

TableJSON 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: +"Das Search Assets input schema. Intent: read/discovery 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."

First observedJul 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: pricing is 'paid read-premium' with an estimate-first workflow, and signer boundary notes that hosted reads never receive keypair bytes. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is somewhat verbose, repeating SAP MCP context and pricing details that also appear in the input schema description. It is structured but could be more concise by removing redundancy.

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?

Given the complexity (9 optional parameters, output schema exists), the description covers purpose, usage, behavioral traits, pricing, and signer boundary. It is largely complete, though error handling and response structure are not mentioned (but output schema covers the latter).

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 each parameter has a description. The tool description mentions filter types (owner, creator, collection, search query) but does not add meaning beyond what the schema already provides. Baseline is appropriate at 3.

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 clearly states the tool searches NFTs/assets with flexible filters via DAS, and specifies use cases (owner, creator, collection, search query). It distinguishes DAS reads from Metaplex writes, but does not explicitly differentiate from similar sibling tools like das_getAssetsByOwner or das_getAsset, leaving some ambiguity about when to use this general search versus those specific tools.

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

Usage Guidelines3/5

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

The description gives clear context for when to use this tool ('use for read-only DAS NFT and asset discovery') and a preference for DAS reads before Metaplex writes. However, it does not explicitly state when not to use it or mention alternatives like das_getAsset for single asset retrieval, leaving room for improvement.

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.