Skip to main content
Glama

Get a song import

get_song_import
Read-onlyIdempotent

One import: queued, fetching, done (with its song) or failed (and why)

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": {
      "import_id": "<import_id>"
    },
    "name": "get_song_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_idYesThe import id (import_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the four lifecycle states, that a completed import carries its song, and that failures include a reason; however it says nothing about what happens for unknown ids or partial states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded fragment with zero filler; the state enumeration is the most decision-relevant information presented first. It is slightly telegraphic, reading as a return-value sketch rather than a full sentence, which costs a point.

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

Completeness3/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 bears the burden of explaining return values, and it does so only as a state sketch, not the import object's fields. For a simple single-parameter read tool this is close to adequate, but the missing id-not-found behavior and field detail leave gaps.

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 coverage is 100% — the single import_id parameter is documented in-schema with its import_… format — so the description carries no obligation here. It restates only the id in the wording 'One import' and adds no constraints beyond the schema, matching the baseline 3.

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?

'One import' plus the enumerated states (queued, fetching, done, failed) makes clear this retrieves a single import record by id rather than a list. No explicit verb is used, but the resource and scope are unambiguous enough to distinguish it from list_song_imports.

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 gives no when-to-use guidance and never references alternatives such as list_song_imports for browsing many imports or cancel_song_import for stopping one. An agent must infer the routing decision from names alone.

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