Skip to main content
Glama

Kariaa Agents

Submit work on a platform

submit_work

Use when the person confirms the work on a platform application is complete and should be sent for review. Sends it as the person.

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": {
      "application_id": "<application_id>"
    },
    "name": "submit_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
application_idYes

Output Schema

NameRequiredDescriptionDefault
stageNoWhere it stands
submittedNoTrue when sent for review
application_idNoThe platform application

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds two pieces of genuinely non-structured context: the action is performed as the person (identity/authority), and it triggers a review state change — both actionable for an agent deciding whether to call it.

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?

Two short sentences, trigger condition front-loaded before the action, no filler or repetition of the title.

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 not be explained, and annotations cover the safety profile. However, for a consequential one-shot submission the description omits whether prior uploads are prerequisites, what `note` conveys to the reviewer, and whether submission is reversible — gaps that matter at call time.

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 the burden, and it mentions neither parameter. It never says which application `application_id` selects, nor what `note` is for or its length limit implications, leaving the agent to infer 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?

The description names a specific verb+resource pair — sending completed work on a platform application for review — which is concrete enough for an agent to act on. The 'platform application' qualifier distinguishes it from other submit/add siblings, 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?

It gives a clear activation condition: only when the person confirms the work is complete and should be sent for review, which correctly gates a consequential action behind human confirmation. It stops short of naming exclusions or an alternative tool for partial or draft submissions.

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.