Skip to main content
Glama

Kariaa Agents

Platforms Kariaa searches

list_platforms
Read-only

Use when the person asks where Kariaa finds paid work, or which freelance, bounty, competition or agent-task platforms they can use. Lists each platform with its category, whether the agent can apply there, and whether the person's account is linked.

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
countNoHow many
platformsNoPlatforms: id, name, category, tier, stages, linked
link_accounts_atNoWhere the person links accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's extra content (listing each platform with category, applicability, and link status) largely restates what the output schema already defines, adding little behavioral context such as freshness or ordering.

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 sentences, both earning their place: the first front-loads the trigger condition, the second states exactly what the result contains. No filler or repetition.

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

Completeness5/5

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

For a zero-parameter read-only tool with an output schema and full annotation coverage, this is complete. An agent knows when to call it and what it will get back without needing further detail.

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 the baseline is 4; there is nothing for the description to disambiguate. The description correctly avoids inventing inputs the schema does not have.

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 pairs a specific verb (lists) with a specific resource (platforms) and even enumerates the fields returned: category, agent-applicability, and account link status. It is clearly distinct from siblings like connect_platform or search_jobs, though it never names an alternative directly.

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 gives an explicit trigger: 'Use when the person asks where Kariaa finds paid work, or which freelance, bounty, competition or agent-task platforms they can use.' That is a clear context for selection, but there is no when-not guidance and no pointer to connect_platform for actually linking an account.

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.