Skip to main content
Glama

Kariaa Agents

Save a job

save_job
Idempotent

Use when the person wants to keep a job from search_jobs on their Kariaa list to come back to. Needs the person signed in.

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": {
      "job_id": "<job_id>"
    },
    "name": "save_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
savedNoTrue when on the list
job_idNoJob id
saved_countNoSaved jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent write (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description's main added value is the auth prerequisite, 'Needs the person signed in,' which is not captured in annotations. It stops short of noting what happens if the job is already saved, though idempotentHint covers that.

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, front-loaded with the usage trigger followed by the prerequisite. No redundant restatement of the title or padding.

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?

An output schema exists, so return values need not be explained, and the auth prerequisite plus the sourcing of the job_id cover the essentials for a single-parameter mutation. Only minor gaps remain, such as duplicate-save behavior and id format.

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 description coverage is 0% for the single job_id parameter, so the description must be the source of meaning. It partially compensates by tying the identifier to jobs obtained from search_jobs, but does not state the expected uuid format or that it must be one saved earlier through this source.

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?

Uses a specific verb ('keep'/save) and resource ('a job from search_jobs') and names the sibling tool the job comes from, so the agent can distinguish it from list or search operations. It does not explicitly differentiate from my_saved_jobs, which is the closest sibling.

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?

Frames the trigger condition clearly: the person wants to keep a job on their Kariaa list to come back to, sourced from search_jobs. No explicit when-not or alternative is given, but the context is unambiguous for this action.

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.