Skip to main content
Glama

EmblemAI AgentWallet

by ai.emblemvault

Ordiscan: searchStamps

searchStamps
Read-onlyIdempotent

Search the Bitcoin Stamps index (Stampchain.io) with multiple filters: free-text query, creator address, collection, Counterparty asset ID, BTC vs cursed filtering, and pagination. Use this for stamp discovery and curated collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpidNoCounterparty asset ID (CPID), e.g. 'A12345...', identifying a specific stamp asset.
pageNo1-indexed page number for paginating results.
limitNoHard cap on total results returned. Use as an alternative to page_size for one-shot calls.
queryNoFree-text query against stamp asset names, descriptions, and metadata.
creatorNoFilter to stamps issued by a specific Bitcoin/Counterparty creator address.
is_cursedNoIf true, only return cursed stamps (out-of-spec issuances); if false, exclude them.
page_sizeNoItems per page (1-100). Defaults to API default.
sort_orderNoResult ordering by stamp number: 'ASC' (oldest first) or 'DESC' (newest first).
is_btc_stampNoIf true, only return canonical BTC Stamps; if false, exclude them.
collection_idNoFilter to stamps belonging to a Stampchain collection ID.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds context beyond that by specifying the data source (Stampchain.io), the filter categories, and pagination behavior, which is valuable for an agent.

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?

Two concise sentences: the first states the action and lists filters, the second gives the intended use case. Every part is informative and no words are wasted.

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?

With 10 optional parameters all fully described in the schema and safe-read annotations, the description effectively covers the tool's purpose and filter breadth. It mentions all major filter categories and pagination, and no output schema is necessary for a straightforward search 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 coverage is 100%, and each parameter already has a meaningful description. The description groups filters into categories (free-text, creator, collection, CPID, BTC vs cursed, pagination) but does not add details beyond what the schema provides.

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 uses a specific verb ('Search') with a clear resource ('Bitcoin Stamps index'), and lists multiple filter dimensions. It distinguishes itself from siblings like getStamp or getStampsByAddress by emphasizing discovery and curated collections.

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

Usage Guidelines4/5

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

The description explicitly states a use case: 'Use this for stamp discovery and curated collections.' It provides clear context but does not name alternative tools or give explicit when-not-to-use guidance.

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

All EmblemAI AgentWallet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation2/5

With 113 tools spanning many chains and asset classes, there is substantial overlap. For example, listPositions and getAllPositions appear to serve the same function, and there are many balance, token discovery, and collection data tools that differ mostly by chain or protocol, making misselection likely.

Naming Consistency2/5

Naming conventions are inconsistent: most tools use camelCase with a verb (baseGetBalances, ethSwapQuote), but some use underscores (nansen_defi_portfolio), others are just bare nouns (wallet, rugcheck), and there are irregularities like solanaBalances instead of solanaGetBalances, plus hederaTokensSwapQuote vs. baseSwapQuote.

Tool Count1/5

The server exposes 113 tools, far beyond the typical well-scoped set. This is an extreme mismatch with the apparent purpose of a wallet/swap server, making discovery and selection difficult for agents.

Completeness2/5

While the server offers extensive read-only data (balances, market data, NFTs, positions), it lacks core write operations: there is no actual swap execution or token transfer tool, and the referenced emblemCreateVault tool is missing. These are significant gaps that will prevent agents from completing common wallet actions.

Resources