Skip to main content
Glama

Supported platforms and prices

list_supported_platforms
Read-onlyIdempotent

List the platforms and link forms fetch_media accepts and the credit cost of every tool. Free, and works without an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_supported_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the description's added value is the cost/auth profile: no credits consumed and no API key needed. That is exactly the kind of operational context annotations cannot express. It does not describe the shape of the response, which keeps it from a 5.

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 content of the response front-loaded and the cost/auth reassurance second. Every clause carries distinct 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 zero-parameter, no-output-schema metadata tool this covers purpose, contents, cost, and auth prerequisites. A brief note on response format would be the only addition, but with no output schema and trivial inputs the definition is close to complete.

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?

The tool takes zero parameters and the schema is empty at 100% coverage, so the baseline is 4. Nothing in the description is needed to explain inputs, and nothing misleading is said about them.

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?

"List the platforms and link forms fetch_media accepts and the credit cost of every tool" gives a specific verb and two concrete resources, and anchors the tool to the sibling it supports (fetch_media). An agent can immediately distinguish this discovery/metadata tool from fetch_media, get_balance, or the youtube_* tools.

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 reference to fetch_media implies the natural occasion to call this (before constructing a fetch_media request or budgeting credits), and "Free, and works without an API key" removes the main precondition an agent might hesitate over. It stops short of an explicit "use this before X instead of trial-and-error" statement, so it is clear context rather than full when/when-not guidance.

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.