Skip to main content
Glama

Kariaa Agents

Add a written answer

add_text_sample

Use when a DataHouse text task wants a written answer. For a text task: the person's written answer (20 to 20,000 characters), stored as a .txt sample.

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": {
      "submission_id": "<submission_id>",
      "text": "<text>"
    },
    "name": "add_text_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
filenameNo
submission_idYes

Output Schema

NameRequiredDescriptionDefault
fileNoThe stored answer
wantedNoSamples the task needs
receivedNoSamples in
ready_to_submitNoAll samples in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write/offline profile is covered structurally. The description adds real context by saying the answer is persisted as a .txt sample, but says nothing about whether this appends or replaces existing samples, permission/precondition failures, or whether the submission must already exist.

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?

Two short sentences with the trigger condition front-loaded and no filler. The 'For a text task:' clause is mildly redundant with the first sentence, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, but the definition leaves the required submission_id completely undefined and gives no hint about how to obtain it (e.g., via get_submission) or what filename controls. For a 3-parameter mutation tool with zero schema description coverage, that is a substantial hole.

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 0%, so the description must carry the load. It explains the meaning of 'text' (the person's written answer) and even restates its 20–20,000 character bounds, but required 'submission_id' and optional 'filename' get no explanation at all, leaving the two most non-obvious inputs undefined.

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+resource ('Add ... a written answer' as a '.txt sample') scoped to DataHouse text tasks, which separates it from generic work-submission siblings like add_work or submit_samples. It never names an alternative explicitly, but the purpose is unambiguous.

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 a DataHouse text task wants a written answer' gives a concrete triggering condition, which is clearer than most siblings' implied usage. It stops short of 5 because it names no exclusions and does not say what to use when the task is not a text task.

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.