Skip to main content
Glama

list_platforms

Read-onlyIdempotent

Lists connected coding platforms and the tags and difficulty levels each accepts as filters, so you can choose valid practice filters.

Instructions

Connected platforms, with the tags and levels each one accepts as filters.

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_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedOutput schema / $defs / PlatformInfo / properties / source
      Added value: +{
      +  "default": "platform",
      +  "title": "Source",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive, open-world operation, covering the safety profile. The description adds that results include accepted tags and levels, but gives no further behavioral detail such as authorization requirements, rate limits, or result shape beyond what the output schema likely covers. With annotations carrying most of the behavioral burden, this is adequate but thin.

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?

The description is a single compact sentence with no filler, and the key output content is front-loaded. It is slightly terse as a sentence fragment, but there is no wasted wording.

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 that there are zero parameters, full annotation coverage, and an output schema, the description is mostly complete: it names the resource and highlights the tags and levels returned. It could say more about when an agent should call it, but nothing needed to invoke it correctly is missing.

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, so there are no parameter semantics for the description to explain. The baseline for a parameterless tool applies, and the description does not introduce misleading parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as connected platforms and notes that it returns tags and levels accepted as filters. However, it is a noun phrase rather than a clear verb+resource statement, so the listing action is only implied by the tool name. It does not distinguish this tool from any sibling by purpose.

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 explicit guidance on when to use this tool, when not to use it, or which alternatives exist. Usage is only implied by the returned content, leaving the agent to infer the correct context.

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