AgentFeed

SPL token metadata

get_token_metadata

Read-onlyIdempotent

SPL token metadata: name, symbol, decimals, supply, price (Helius DAS). Costs 0.005 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mint`	Yes	SPL token mint address (base58)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_token_metadata payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_token_metadata
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

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"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable non-obvious context: the per-call cost of 0.005 USDC, the x402 payment mechanism, and the Helius DAS backend. This exceeds what the annotations alone provide without contradicting them.

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 terse sentences: the first front-loads what the tool returns, and the second states the cost and payment rails. Every clause earns its place with no filler.

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 one fully documented required parameter, rich safety annotations, and an output schema, the description only needed to add non-obvious constraints like cost, which it does. An agent has everything it needs to invoke this tool correctly.

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?

The schema fully documents the single `mint` parameter as an SPL token mint address in base58, so the description does not need to compensate. The description adds no new parameter-level meaning beyond what the schema already states.

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 identifies the exact resource (SPL token metadata) and lists the returned fields (name, symbol, decimals, supply, price), so an agent can tell what it provides. It is not phrased as a full verb sentence, but it is specific enough to distinguish it from siblings like get_token_holders or get_token_risk.

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 the tool should be used when SPL token metadata is needed, and the cost disclosure is a relevant usage constraint. However, it does not explicitly say when to prefer this over related token tools or mention any alternative.

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

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