Skip to main content
Glama

AI Training Jobs

List platforms

list_platforms
Read-onlyIdempotent

Every platform listed, with open jobs, median top hourly rate, beginner-friendly roles and a one-line description. Use get_platform for how to get accepted and how it pays.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing what each result contains (open job counts, median top hourly rate, beginner-friendly flag, one-line blurb), which is the main behavioral fact an agent needs. It stops short of noting ordering, result count, or currency normalization for the rates.

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 tight sentences: the payload comes first, the sibling routing second. No filler, no restatement of the title, and every clause conveys new 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?

With no output schema, the description carries the burden of describing return values and it does so field by field, which is the key gap it needed to fill. Remaining omissions (ordering, total count, rate units) are minor for a zero-parameter read-only list.

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 is nothing for the description to disambiguate; the schema is trivially complete. Baseline 4 applies since no parameter guidance is needed or expected.

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 makes clear this returns the full set of platforms ('Every platform listed') and enumerates the per-entry payload: open jobs, median top hourly rate, beginner-friendly roles, and a one-line description. The verb is implicit rather than stated, but the resource and scope are unambiguous and distinguishable from get_platform.

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?

It explicitly routes the agent away to a sibling: 'Use get_platform for how to get accepted and how it pays,' which cleanly separates browsing the catalog from drilling into one platform's onboarding and payment details. It does not state an explicit when-to-use trigger for this tool itself, but the browse-vs-detail split is clear.

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