Skip to main content
Glama

Kariaa Agents

Link an account on a platform

connect_platform
Read-only

Use when applying on a platform needs the person's own account there (get_job or apply_to_work said so). Returns the link where the person signs in to that platform or lets Kariaa set the account up. The person opens it; the agent never handles their password.

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": {
      "platform": "<platform>"
    },
    "name": "connect_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesA platform id from list_platforms or a job_id prefix, e.g. kaggle

Output Schema

NameRequiredDescriptionDefault
urlNoWhere the person links it
platformNoPlatform id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds context beyond the readOnly/non-destructive annotations: the result is a link the person opens, and the agent must never handle the password. It also notes Kariaa may set the account up, though it does not explain what happens if the platform is already linked.

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?

Three short sentences, front-loaded with the trigger condition and followed by the return behavior and the password-handling constraint. No sentence repeats the title or schema.

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 one-parameter linking tool with annotations and an output schema, the description covers the trigger, the interaction model, and the security boundary. It is complete enough to invoke correctly without explaining return fields the output schema already defines.

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?

The only parameter is platform, and the schema already documents it fully with a source (list_platforms or job_id prefix) and an example. The description does not add format or validation details beyond that 100%-covered schema, so it sits at the baseline.

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?

States a specific verb and resource — connecting a platform account — and frames the output as a sign-in or setup link. It distinguishes the tool from apply_to_work and get_job by positioning it as the follow-up those tools may require.

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?

Gives an explicit trigger: use when get_job or apply_to_work indicated the person needs their own account on the platform. It does not name an alternative for obtaining credentials or state when not to use it, so it stops short of full routing 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.