Skip to main content
Glama

Kariaa Agents

Submit the samples

submit_samples
Idempotent

Use when every sample is in and the person confirms. Send the staged samples of a task for review. Needs every sample the task asks for. Optional text_response for notes.

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>"
    },
    "name": "submit_samples"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYes
text_responseNo

Output Schema

NameRequiredDescriptionDefault
submittedNoTrue when sent for review
files_countNoFiles sent
submitted_atNoWhen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotent=true, destructive=false, readOnly=false, so safety is covered. The description adds a genuine precondition beyond that: every sample the task asks for must be present before calling, plus the existence of an optional free-text field. It does not say what happens if samples are missing or whether the submission is final/locked, 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?

Three short sentences with the trigger condition front-loaded and no filler. The clipped phrasing ('Needs every sample the task asks for') trades a little clarity for brevity, but nothing is wasted.

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

Completeness3/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 no description, and the annotations cover safety. Still, the critical required submission_id is undocumented and the description omits the staging-to-submission lifecycle context an agent needs to call this correctly, which is thin for a finalizing action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for both parameters. It explains text_response only obliquely as 'notes' (no length or purpose guidance despite a 5000-char cap), and never explains submission_id — the sole required parameter, whose provenance (get_submission? my_submissions?) an agent must guess.

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: 'Send the staged samples of a task for review.' That distinguishes a final submission action from staging tools like add_text_sample. It does not, however, differentiate itself from the sibling submit_work, leaving ambiguity about which submission endpoint applies to which object.

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?

Gives an explicit trigger condition: 'Use when every sample is in and the person confirms.' That is real when-to-use guidance tied to a prerequisite state and a human confirmation gate. It offers no exclusions or named alternatives, so it stops short of a 5.

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.