Skip to main content
Glama

Kariaa Agents

Remove a sample before submitting

remove_sample
DestructiveIdempotent

Use when the person wants to replace a staged sample. Take back one staged sample (a wrong or bad file) so another can be uploaded in its place. Only before submit_samples. file_id comes from confirm_upload, get_submission or my_submissions.

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

Input Schema

NameRequiredDescriptionDefault
file_idYes
submission_idYes

Output Schema

NameRequiredDescriptionDefault
wantedNoSamples the task needs
removedNoThe sample taken back
receivedNoSamples in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the description doesn't need to argue that data is removed. It still adds real value by disclosing the sequencing precondition (must run before submit_samples) and by characterizing the target as a 'wrong or bad file'. It stops short of saying whether the removed sample is recoverable or what state the submission is left in.

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 short sentences, front-loaded with the trigger condition, then the action, then the precondition and parameter provenance. No restatement of the tool name or filler.

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?

With an output schema present, return values needn't be described, and the destructive semantics are covered by annotations plus the sequencing note. The remaining gap is minor: nothing is said about failure modes (e.g. what happens if the submission has already been submitted) beyond the 'only before submit_samples' rule.

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

Parameters4/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 burden, and it usefully documents file_id provenance ('comes from confirm_upload, get_submission or my_submissions'), which the schema does not. submission_id is left implicit, presumably as the owning staging context, so it isn't a complete substitute for the empty schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb-plus-resource framing ('Take back one staged sample') and immediately scopes it to a specific intent ('replace a staged sample ... so another can be uploaded in its place'). That intent is clearly distinct from ingest siblings like confirm_upload or finalization via submit_samples.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering situation ('Use when the person wants to replace a staged sample') and an explicit guardrail ('Only before submit_samples'), which is the critical when-not condition. The referenced sources of file_id also indirectly point at the upload/inspection tools in the lifecycle.

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.