Skip to main content
Glama
jun229

truemarkets-mcp-server

by jun229

List available tokens

tm_list_assets
Read-onlyIdempotent

Retrieve a list of all tradable tokens on True Markets, with optional filtering by blockchain network (Solana or Base) to view available assets.

Instructions

List all tokens available for trading on True Markets.

Args:

  • chain (string, optional): Filter by "solana" or "base"

Returns: Array of { symbol, name, chain, address }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoFilter by chain

Implementation Reference

  • Handler function for tm_list_assets tool that retrieves and filters assets from the API.
    async ({ chain }) => {
      let assets = await api.getAssets();
    
      if (chain) {
        assets = assets.filter(
          (a) => a.chain?.toLowerCase() === chain
        );
      }
    
      const items = assets.map((a) => ({
        symbol: a.symbol ?? "",
        name: a.name ?? "",
        chain: a.chain ?? "",
        address: a.address ?? "",
      }));
    
      const output = { count: items.length, assets: items };
    
      return {
        content: [{ type: "text", text: JSON.stringify(output, null, 2) }],
        structuredContent: output,
      };
  • Registration of the tm_list_assets tool, including its schema and metadata.
      server.registerTool(
        "tm_list_assets",
        {
          title: "List available tokens",
          description: `List all tokens available for trading on True Markets.
    
    Args:
      - chain (string, optional): Filter by "solana" or "base"
    
    Returns: Array of { symbol, name, chain, address }`,
          inputSchema: {
            chain: z.enum(["solana", "base"]).optional().describe("Filter by chain"),
          },
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
        },
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, indicating a safe, non-destructive, and repeatable read operation. The description adds context by specifying the return format (array of symbol, name, chain, address), which is valuable beyond annotations, though it doesn't detail rate limits or authentication needs.

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 front-loaded with the core purpose, followed by clear Arg and Return sections. Every sentence earns its place by efficiently conveying essential information without redundancy, making it appropriately sized and well-structured for quick understanding.

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?

Given the tool's low complexity (one optional parameter) and rich annotations covering safety and behavior, the description is mostly complete. It specifies the return format, which compensates for the lack of an output schema. However, it could improve by mentioning authentication or rate limits, though annotations provide sufficient context for a read-only operation.

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 description coverage is 100%, with the schema fully documenting the optional 'chain' parameter and its enum values. The description adds minimal value beyond the schema by restating the filter purpose, but doesn't provide additional syntax or format details, aligning with the baseline score when schema coverage is high.

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?

The description clearly states the verb 'List' and the resource 'tokens available for trading on True Markets', making the purpose specific. It distinguishes from siblings like tm_get_balances (which retrieves user balances) and tm_get_price (which fetches pricing data) by focusing on available trading tokens rather than user-specific or price information.

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 usage for listing tokens, but does not explicitly state when to use this tool versus alternatives. For example, it doesn't clarify if this should be used before trading or as a reference, nor does it mention exclusions or direct comparisons to siblings like tm_get_rades or tm_prepare_transfer, leaving usage context inferred rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jun229/tm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server