Skip to main content
Glama

jobsuche_list_offers

List and filter tracked Ausbildung offers stored in SQLite by city, company, status, minimum score, and limit to review and manage application progress.

Instructions

List and filter tracked Ausbildung offers stored in SQLite.

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": "jobsuche_list_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoFilter by city name.
limitNoMaximum number of offers to return.
statusNoFilter by application status.
companyNoFilter by company name or slug.
db_pathNoOptional override path for SQLite database.
min_scoreNoFilter by minimum relevance score (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the read-oriented nature ("List and filter") and the SQLite backing store, but says nothing about default limits, ordering, whether filters combine with AND, or whether db_path overrides are risky.

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?

A single front-loaded sentence with zero filler, and the key noun phrase comes first. It is efficient, though so terse that it borders on under-specification rather than being trim.

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?

With six optional parameters, no annotations, and no output schema, the definition should say more about what a returned offer looks like and how the optional filters compose. The description does not compensate for the missing annotation layer.

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 100%, so every parameter including the status enum and the db_path override is already documented in the schema. The description adds only the implicit link between the SQLite mention and db_path; baseline 3 applies.

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 pair ("List and filter") and a specific resource ("tracked Ausbildung offers"), plus the storage backend (SQLite). That distinguishes it reasonably from jobsuche_search_ausbildung, but it never explicitly states the local/tracked-vs-search boundary, so the differentiation is inferred rather than declared.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The word "tracked" hints that this operates on already-captured records rather than running a new search, but an agent must infer that on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.