Skip to main content
Glama
Sign In

Souvenir

by finance.souvenir
OverviewDiscussionsAdmin

Get a Souvenir coin

get_coin
Read-only

One coin by its mint address, as search_coins lists it: 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. A coin that is not on Souvenir is not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint": "<mint>"
    },
    "name": "get_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesThe coin's mint address (base58).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes well beyond that by explaining the meaning of every returned field — venue values (pump, meteora, bags), origin (launched vs brought), the three mode semantics, potSol, prize composition, the latest unfinished round, and holder snapshot timing — which is essential disclosure given there is no output schema.

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?

A single sentence, front-loaded with the core purpose, followed by parenthetical field glosses. It is dense and long, but with no output schema every enumerated field earns its place; only slight tightening would improve readability.

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?

For a one-parameter lookup with no output schema, the description covers everything an agent needs: how to identify the coin, the exact shape and semantics of the response, and the not-found outcome. Nothing material is left to inference.

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%, with the mint parameter documented as a base58 address and constrained by a regex pattern. The description adds only the not-found caveat for coins outside Souvenir; otherwise it defers to the schema, so the baseline 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?

"One coin by its mint address" states a specific verb and resource, and the reference to search_coins immediately separates this single-item lookup from its list sibling. The enumeration of returned fields reinforces exactly what a caller gets back.

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 frames this as the counterpart to search_coins (which lists coins) and adds a clear boundary condition: "A coin that is not on Souvenir is not found." It does not spell out an explicit when-not-to-use case, but the context is unambiguous for a lookup-by-identifier tool.

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