Skip to main content
Glama

Kariaa Agents

List DataHouse tasks

list_tasks
Read-only

Use when the person wants paid data tasks from Kariaa (record clips, photos, voice, label text). The open DataHouse tasks: title, kind (video, photo, voice, text), the unpaid verification sample each wants and the rate paid work earns after verification. No key needed. Filter by file kind.

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_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly tasks that take this file kind
limitNoDefault 25

Output Schema

NameRequiredDescriptionDefault
countNoHow many
tasksNoOpen DataHouse tasks: task_id, title, summary, sample, pay, allowed_file_kinds, url
signed_inNoWhether a key was sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 adds genuinely new behavioral context: no API key is required, and it discloses the shape of each result including the unpaid verification sample requirement and post-verification rate, which is non-obvious domain behavior.

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 tight sentences, front-loaded with the 'Use when' trigger, then the return contents, then the auth and filtering notes. No filler and nothing redundant with the structured fields.

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 two-parameter, annotation-covered read tool with an output schema, the definition supplies trigger, auth requirement, and domain context (verification sample, rates) that an agent would otherwise have to guess. The one gap is no mention of paging behavior beyond the schema's limit bounds, but the output schema absorbs most return-value concerns.

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 description coverage is 100%, so the baseline is 3. The description's 'Filter by file kind' restates the kind parameter without adding format or default details, and it says nothing about the limit parameter or its 25 default, leaving the schema to carry both.

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?

States a specific verb and resource: lists open DataHouse tasks from Kariaa, and enumerates what each listing contains (title, kind, verification sample, rate). An agent can tell this is a browse/open-task listing rather than a detail or application tool, though no sibling is named explicitly.

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 wants paid data tasks from Kariaa' gives a clear positive trigger and the parenthetical (record clips, photos, voice, label text) reinforces the context. There is no explicit when-not or named alternative, 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.