Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

SPL token metadata

get_token_metadata
Read-onlyIdempotent

SPL token metadata: name, symbol, URI, decimals, supply, mint and freeze authority, mutability. Read from the mint account and its metadata account. Costs 0.005 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

NameRequiredDescriptionDefault
mintYesSPL token mint address (base58)

Output Schema

NameRequiredDescriptionDefault
dataYesthe get_token_metadata payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_token_metadata
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / mint / maxLength
      Added value: +44
    • addedInput schema / properties / mint / minLength
      Added value: +32
    • addedInput schema / properties / mint / pattern
      Added value: +"^[1-9A-HJ-NP-Za-km-z]{32,44}$"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_token_metadata payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_token_metadata",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_token_metadata",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's marginal value comes from disclosing the data source (mint account plus metadata account) and, importantly, that the call is paid — 0.005 USDC via x402 on five named chains. That payment requirement is critical context an agent cannot get from structured fields. It stops short of explaining behavior for mints with no metadata account (legacy vs Token-2022) or error cases.

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 sentences, zero filler. The returned-field list is front-loaded and the operational constraint (cost, payment rails) is packed into the second sentence.

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?

An output schema exists, so return values need not be described, and the cost/payment surface is covered. The main remaining gap is edge-case behavior — what is returned for a mint lacking a metadata account — which matters for a paid call.

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 the single parameter already carries a base58 pattern plus a description, so the schema does the work. The description only echoes that data is read from the mint account, adding no format or validation detail beyond what is structured.

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 names a specific resource (SPL token metadata) and enumerates the exact fields returned — name, symbol, URI, decimals, supply, authorities, mutability — which lets an agent distinguish it from siblings like get_token_holders, get_token_risk, or get_sol_token_check. It lacks an explicit contrast sentence naming those siblings, keeping it just below a 5.

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?

Usage is only implied: an agent can infer this is the lookup for token-level facts given a mint address. There is no statement of when to prefer this over get_sol_token_check or get_token_risk, and no prerequisites or exclusions beyond the cost disclosure.

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

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