Skip to main content
Glama

Kariaa Agents

My saved jobs

my_saved_jobs
Read-only

Use when the person asks for the jobs they saved: newest first, with whether each is still open. Needs the person signed in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_saved_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
jobsNoSaved jobs, newest first, with whether each is still open
countNoHow many

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive and closed-world, so the description earns credit for what it adds: the result ordering (newest first), the inclusion of open/closed status per job, and the sign-in requirement. It goes beyond the structured metadata without contradicting it. An output schema exists, so not describing the return shape is acceptable.

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?

A single sentence with the trigger clause first, followed by the result characteristics and the prerequisite — every clause carries information and none is redundant.

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 parameterless read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: when to call it, who must be authenticated, and what the results will look like. No material gap remains.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate beyond the implicit scoping to the signed-in person, which it does imply.

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?

States a specific verb-resource pair ('the jobs they saved') plus the ordering ('newest first') and included field ('whether each is still open'), which is enough to distinguish it from search_jobs (general lookup) and save_job (the write counterpart). It falls short of a 5 only because it doesn't explicitly name the read/write counterpart it complements.

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?

'Use when the person asks for the jobs they saved' gives a concrete trigger condition, and 'Needs the person signed in' states a prerequisite. There is no explicit when-not or named alternative for the case where the user wants a broader job search.

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.