Skip to main content
Glama
Sign In

Souvenir

by finance.souvenir
OverviewDiscussionsAdmin

Search Souvenir coins

search_coins
Read-only

Lists coins on Souvenir, searched and sorted. Answers { coins, nextCursor }. Each coin: mint, symbol, name, image, venue (pump, meteora or bags), origin (launched on Souvenir or brought), mode (full: its rounds draw an item; draws: they pay drawSol in SOL; prizes: its creator awards prizes), potSol (the open pot), prize (full mode: id, image, priceUsd), round (the latest unfinished one: number, state, targetSol, potSol), holders (at the latest snapshot) and links. For the next page, pass nextCursor back as cursor; it is null on the last page. Coins whose prize is adult (NSFW) are left out, as on the site, unless nsfw is true.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch: a coin's name or ticker ($ optional), its prize's name, or the start of its mint.
nsfwNotrue to list coins whose prize is adult (NSFW) too; left out by default.
sortNopot: the largest open pot first. new: the newest launch first. drawing: the closest to its next draw first (the pot nearest its target). holders: the most holders first.pot
limitNoCoins a page.
venueNoOnly coins trading there: pump.fun, Meteora or Bags.
cursorNoThe last page's nextCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish readOnlyHint and openWorldHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: NSFW coins are excluded by default unless nsfw is true, nextCursor is null on the last page, and the response shape is explained in detail.

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 front-loaded with purpose and return shape, then moves into pagination and filtering. The long field enumeration is dense but justified because there is no output schema, and there is little wasted wording.

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 there is no output schema, the description does a thorough job explaining the returned coin fields and nextCursor pagination. It also documents the NSFW exclusion behavior. The main gap is that it does not compare itself to sibling lookup tools.

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%, so the input schema already explains q, nsfw, sort, limit, venue, and cursor. The description restates some of that behavior, particularly cursor pagination and NSFW filtering, but adds little parameter meaning beyond what the schema already provides.

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 a specific verb and resource: it lists and searches coins on Souvenir, with sorting and pagination. It does not explicitly differentiate itself from siblings like get_coin or get_rounds, so it falls short of a 5 on sibling differentiation.

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 implies usage for searching and listing coins and gives clear pagination guidance for passing nextCursor back as cursor. However, it does not explicitly say when to use this tool versus get_coin or get_rounds, nor does it state exclusions or alternatives beyond the NSFW default.

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

All Souvenir 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