Skip to main content
Glama

Kariaa Agents

Get a DataHouse task

get_task
Read-only

Use when the person picks a DataHouse task. One task in full: description, the task's own material (instructions: the sentences to read, texts to label, answers to rate), the unpaid verification sample with how-to steps and rules, allowed file kinds, the qualification questions (with ids, for apply_to_task) and the rate paid work earns after verification.

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": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
payNoRate for paid work after verification
nextNoThe next tool
rulesNoTask rules
titleNoTitle
sampleNoThe unpaid verification sample: count, instructions, how_to, looks_like
task_idNoTask id
instructionsNoThe task's own material: sentences to read, texts to label, answers to rate
program_rulesNoRules for every task
qualification_questionsNoQuestions to answer in apply_to_task, with ids

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 cover read-only, non-destructive, closed-world behavior, and the description adds real value by disclosing the returned contents, including that qualification questions carry ids meant for apply_to_task, and that pay applies only after verification. It says nothing about behavior for a missing/invalid task id or access restrictions, which is the remaining gap.

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 condition is front-loaded in the first clause, and the second sentence is a dense but purposeful inventory of what comes back. The nested parentheticals ("instructions: the sentences to read, texts to label...") make it slightly crowded, but no sentence is wasted.

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?

For a one-parameter read tool with annotations and an output schema, the definition covers trigger, payload, and the hand-off to apply_to_task. Missing is any guidance on sourcing a valid task_id or what happens when the id is unknown, which is the only material omission.

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?

There is a single required task_id parameter with no schema description (0% coverage), and the description never mentions it or how to obtain it. The schema's uuid format is the only hint the agent gets, so the description adds essentially no parameter meaning beyond structured data.

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 exactly one DataHouse task in full and enumerates the payload components (description, task material, verification sample, allowed file kinds, qualification questions, pay rate). It is specific about the verb and resource, though it relies on the name/title to convey the 'by id' lookup aspect and never distinguishes itself from siblings like get_job or get_submission.

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?

"Use when the person picks a DataHouse task" gives a concrete triggering condition for invocation. It stops short of naming an alternative (e.g., list_tasks for browsing before selection) or stating when not to call it, so it is clear context without exclusions.

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.