Skip to main content
Glama

Kariaa Agents

Confirm an uploaded sample

confirm_upload
Idempotent

Use right after the PUT from request_upload. After the PUT: register the object at path as a sample of the task. Returns how many samples are in and how many the task wants.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
submission_idYes

Output Schema

NameRequiredDescriptionDefault
fileNoThe registered sample
wantedNoSamples the task needs
receivedNoSamples in
ready_to_submitNoAll samples in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already cover the safety profile: mutation, idempotency, non-destructive, and closed-world. The description adds useful sequencing context and notes that counts are returned, but it does not explain retry behavior or what happens if invocation is out of order. It adds some value beyond annotations without fully characterizing the operation.

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 description is short, front-loaded with the timing constraint, and has no filler. There is minor redundancy between 'Use right after the PUT' and 'After the PUT', but it remains efficient.

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?

For a two-parameter mutation tool, the description adequately explains sequencing and action, and the output schema covers return values. However, it omits what `submission_id` identifies and does not address failure or preconditions, leaving a required parameter under-specified.

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 must carry parameter meaning. It explains `path` by referring to 'the object at `path`', but `submission_id` is never mentioned at all. For two required parameters, that leaves a significant gap.

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 states a specific action: register the object at `path` as a sample of the task. It also names the predecessor `request_upload`, which helps distinguish it from the upload step itself. It stops short of explicitly differentiating it from other sample-submission siblings, but the core purpose is clear.

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 gives explicit timing guidance: 'Use right after the PUT from request_upload' and reinforces 'After the PUT'. That is enough context to know when to call it. It does not state when not to use it or name alternatives, so it falls 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.