Skip to main content
Glama

Kariaa Agents

Apply to paid work on a platform

apply_to_work

Use when the person says yes to applying for a paid task, bounty, competition or freelance project from search_jobs (a job_id like "kaggle:titanic"). Applies as the person through their linked account. Ask them first and pass any note they want sent. For job openings with a UUID job_id, the person applies on the employer's page instead.

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": {
      "job_id": "<job_id>"
    },
    "name": "apply_to_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoCover note or proposal text, in the person's words
job_idYesA platform job_id from search_jobs, connector:id

Output Schema

NameRequiredDescriptionDefault
nextNoWhat to do next
stageNoapplied, work_needed, in_review…
job_idNoJob
appliedNoTrue when sent
application_idNoThe platform application

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint, non-idempotent, non-destructive) it discloses two things the annotations cannot: the call acts as the person through their linked account, and human confirmation must precede it. What is missing is failure behaviour — e.g. what happens if the application is rejected or how retries interact with a non-idempotent submit.

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 usage trigger, then the actor/consent requirement, then the fallback case. No redundant or decorative wording.

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 two-parameter action tool with an output schema, the description supplies everything needed to call it correctly: when to invoke, required consent, and when a given job_id is out of scope. Return values need not be explained because the output schema covers them.

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?

Schema coverage is 100%, so both parameters are already documented, and the description largely echoes the schema (note in the person's words, connector:id job_id). The concrete "kaggle:titanic" example adds a small amount of clarity but no new semantics for either parameter.

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?

Names a specific verb (applies) plus the resource (paid task, bounty, competition or freelance project) and states the source of the job_id (search_jobs, format "kaggle:titanic"). It also draws a scope boundary: job openings with a UUID job_id are handled on the employer's page rather than here.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger (the person says yes to applying), a precondition (ask them first), and an exclusion (UUID job_id openings go through the employer's page). It also directs the agent to pass along any note the person wants sent.

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.