Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

What a mint declares, and whether it can change

singularityagent__token_identity
Read-only

Read what a Solana mint says it is — its name, ticker, metadata link — and, crucially, whether any of that can be rewritten later at the same address. Where the update authority is revoked and the link is content-addressed (an IPFS CID), what the mint declares is fixed at mint time and cannot be swapped. Set fetch to also read the document and return the accounts it declares (X, Telegram, website, GitHub); it is off by default because the link is a URL chosen by whoever deployed the mint. Use it to answer whether a token, or an account claiming to represent one, is the real one — the answer is always the mint address, never the ticker. A mint wearing a curated token’s symbol or name at a different address is reported as impersonation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesMint address, or an address-book alias for one.
chainNoSolana chain id or alias. Defaults to "solana".
fetchNoAlso fetch the metadata document and read the accounts it declares. Off by default: it is an outbound request to a URL the deployer chose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "chain": {
+    "description": "Solana chain id or alias. Defaults to \"solana\".",
+    "type": "string"
+  },
+  "fetch": {
+    "description": "Also fetch the metadata document and read the accounts it declares. Off by default: it is an outbound request to a URL the deployer chose.",
+    "type": "boolean"
+  },
+  "mint": {
+    "description": "Mint address, or an address-book alias for one.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "mint"
+]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that fetch is off by default because the metadata link is a URL chosen by the deployer, explains the fixed-when-revoked-and-CID condition, and warns that impersonating curated symbols is reported. This is rich behavioral context that annotations alone do not provide.

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?

The description is longer than average but every sentence carries a distinct behavioral fact: the read scope, mutability rule, fetch behavior and rationale, and impersonation handling. It is front-loaded with the core purpose before diving into details.

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?

With no output schema, the description does a good job covering return categories (identity fields, declared accounts, impersonation status) and edge cases such as revoked update authority. A slight gap is the absence of a concrete return-shape or example response, but the description is sufficient for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value for fetch, specifying it 'also read the document and return the accounts it declares (X, Telegram, website, GitHub),' plus the security rationale for the default. It does not add detail for mint or chain, but those are adequately covered by the schema.

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 opens with a specific verb and resource ('Read what a Solana mint says it is') and states the core output: name, ticker, metadata link, and mutability. It also frames the tool's purpose as verifying whether a token/account is the real one, but it does not explicitly name or contrast sibling tools like singularityagent__mint_audit or singularityagent__resolve.

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 gives an explicit when-to-use instruction: 'Use it to answer whether a token, or an account claiming to represent one, is the real one.' It does not provide when-not-to-use guidance or alternative tool names, but the context is clear enough for routing.

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

All Rokha toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources