Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_track_info

Retrieve Spotify track details including artist, album, and metadata by providing a track ID through the Multi-MCPs server's unified API integration.

Instructions

Get Spotify track details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_idYes

Implementation Reference

  • The handler function that implements the core logic of the 'get_track_info' tool. It validates the Spotify configuration and track_id parameter before calling the SpotifyClient's getTrack method to fetch track details.
    async get_track_info(args: Record<string, unknown>) {
      if (!cfg.spotifyClientId || !cfg.spotifyClientSecret) throw new Error("SPOTIFY_CLIENT_ID/SECRET are not configured");
      const trackId = String(args.track_id || "");
      if (!trackId) throw new Error("track_id is required");
      return client.getTrack(trackId);
    },
  • The input schema defining the required 'track_id' string parameter for the 'get_track_info' tool.
    inputSchema: {
      type: "object",
      properties: { track_id: { type: "string" } },
      required: ["track_id"],
    },
  • The tool registration definition within the Spotify API module, including name, description, and schema.
    {
      name: "get_track_info",
      description: "Get Spotify track details",
      inputSchema: {
        type: "object",
        properties: { track_id: { type: "string" } },
        required: ["track_id"],
      },
    },
  • The invocation of registerSpotify() in the central tool registration function, which incorporates the 'get_track_info' tool into the MCP server.
    registerSpotify(),
  • The SpotifyClient helper method that performs the actual API request to retrieve track information by ID.
    async getTrack(trackId: string) {
      return this.request(`/tracks/${trackId}`, { headers: await this.authHeaders() });
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether authentication is required, rate limits apply, what format the details include, or if there are any side effects. This leaves significant gaps for a tool interacting with an external API.

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 extremely concise with just three words, front-loading the core purpose without any fluff. Every word earns its place, making it efficient for quick scanning while remaining clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and 0% parameter documentation, the description is insufficiently complete. It doesn't explain what 'details' include, how to obtain track IDs, or any behavioral constraints, leaving the agent with inadequate context to use the tool effectively.

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

Parameters2/5

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

With 0% schema description coverage for the single parameter 'track_id', the description adds no semantic information about what this parameter represents, its expected format (e.g., Spotify URI, ID string), or where to obtain it. The description doesn't compensate for the schema's lack of documentation.

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 'Get Spotify track details' clearly states the verb ('Get') and resource ('Spotify track details'), making the purpose immediately understandable. It's specific enough to distinguish this as a retrieval operation for music tracks from Spotify, though it doesn't explicitly differentiate from sibling tools like 'search_tracks' or 'add_tracks_to_playlist'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'search_tracks' available, there's no indication whether this is for retrieving specific known tracks versus searching for tracks, nor any mention of prerequisites or context for usage.

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/TaylorChen/muti-mcps'

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