Skip to main content
Glama

Kariaa Agents

Add work to an application

add_work

Use when the person has finished the work for a platform application (from apply_to_work) and wants it attached: the answer, write-up, code or links as text. Call submit_work after.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe work itself, or links to it
application_idYes

Output Schema

NameRequiredDescriptionDefault
addedNoTrue when attached
application_idNoThe platform application

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds useful pipeline context (this precedes submit_work and follows apply_to_work), but says nothing about what happens if work is added twice or whether existing content is overwritten.

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?

Front-loaded with "Use when," and the follow-up call is packed into a short imperative at the end. Two sentences, no filler; slight density in the first sentence but nothing wasted.

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

Completeness5/5

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

For a simple two-parameter tool with an output schema and rich annotations, the description supplies everything an agent needs: the trigger condition, the upstream source of the application_id, and the required next step. Return values are covered by the output schema.

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 coverage is only 50%: text is documented in the schema, application_id is not. The description compensates partially by explaining that text is "the answer, write-up, code or links" and that application_id comes from apply_to_work, which is meaningful added context, but it does not clarify the expected ID format or whether it is the application or task identifier.

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?

"Use when the person has finished the work for a platform application ... and wants it attached" states a concrete action (attaching work text) and resource (a platform application originating from apply_to_work). It clearly separates the tool from apply_to_work and submit_work, though the operative verb is phrased as user intent rather than as a discrete operation.

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 names the precondition (work has been completed for an application created by apply_to_work) and an explicit follow-up step in "Call submit_work after." That is strong sequencing guidance; the only gap is no explicit exclusion saying when not to call this tool.

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.