Skip to main content
Glama

Kariaa Agents

Apply to a task

apply_to_task
Idempotent

Use when the person wants to join a DataHouse task. Join a DataHouse task for the person. answers maps each question id from get_task to the answer (a string, or a list for multiselect); every required question needs one. Optional preferred rate in their words ("$2 per clip"). One application per task; a task with a sample unlocks its sample step at once.

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": {
      "task_id": "<task_id>"
    },
    "name": "apply_to_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
answersNo
task_idYes
preferred_rateNo

Output Schema

NameRequiredDescriptionDefault
nextNoThe next tool
stageNosample_needed or pending_review
submission_idNoThe application
already_appliedNoTrue when it existed
sample_requirementsNoWhat to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds non-obvious behavior: a hard one-application-per-task limit and the side effect that a task with a sample immediately unlocks its sample step. It does not say what the response is or what error surfaces on a duplicate attempt.

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 trigger is front-loaded and every sentence carries information, with no filler. The telegraphic fragments ('One application per task; a task with a sample unlocks its sample step at once.') pack two distinct behavioral facts into one line, which slightly hurts scanability.

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?

An output schema exists, so return values need not be described, and the definition covers the trigger, required answers, the one-application limit, and rate format. The remaining gap is a nested answers object whose per-field constraints and the role of 'note' are only partly addressed.

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 0%, so the description carries the full burden. It explains the hardest parameter well (answers maps get_task question ids to a string or list for multiselect, and every required question needs an answer) and gives a preferred_rate example, but leaves 'note' entirely unexplained and never clarifies task_id beyond its implicit role.

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 gives a specific verb and resource: 'Join a DataHouse task for the person,' plus a clear trigger sentence. It does not, however, distinguish this from the sibling 'apply_to_work', so an agent must infer the boundary from the noun (task vs. work).

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 states the when ('Use when the person wants to join a DataHouse task') and names the prerequisite source for answers ('question id from get_task'), which gives real ordering guidance. It stops short of explicit exclusions or naming the alternative tool for a related action.

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.