Skip to main content
Glama

solknife_owned_mints_list

List mints the owner is the mint or freeze authority of, found through the owner's token accounts. Feeds the mint picker of the authority and metadata tools.

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": {
      "owner": "<owner>"
    },
    "name": "solknife_owned_mints_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesA Solana address in base58, 32-44 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load, and it does disclose a genuinely important behavioral trait: results are derived from the owner's token accounts, which implies mints where the owner holds authority but has no token account may be missed. It does not cover permissions needed, result size, ordering, or pagination, so it is good but not complete.

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 short sentences, zero filler, with the scoping condition front-loaded before the downstream-use note. Nothing could be removed without losing information.

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?

For a single-parameter read-only list with no output schema, the description covers purpose, derivation mechanism, and downstream consumption, which is enough to call it correctly. It could say slightly more about what each list entry contains, but the tool's simplicity keeps the gap minor.

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?

One parameter at 100% schema coverage, where the schema already states the base58 address format and length constraint. The description adds no further meaning about the owner argument (e.g., that both mint and freeze authority roles are matched against the same field), so 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?

States a specific verb ('List'), an exact resource ('mints'), and the precise qualifying condition ('the owner is the mint or freeze authority of'). The additional discovery mechanism ('found through the owner's token accounts') makes the result set unambiguous and clearly separates it from supply/authority read tools in the sibling list.

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 second sentence explains where the output is consumed ('Feeds the mint picker of the authority and metadata tools'), which tells an agent when this tool is the right upstream call. It stops short of naming explicit alternatives or exclusions (e.g., 'do not use to enumerate all mints, use X'), so it lands at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources