Skip to main content
Glama

stellenonline.de Jobsuche

Get total job count

get_total_jobs
Read-onlyIdempotent

Get the total number of jobs in the database (no filters). Returns structured JSON.

Returns the complete job count. Use this to check the overall index size.

Returns: On success: {"total_jobs": int} On error: {"error": str}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the 'no filters' scope and a return shape, but the return shape is already formalized in the output schema, so net new behavioral information is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key fact, but 'Returns structured JSON' plus 'Returns the complete job count' plus a Returns block restate the same idea three times, and the return payload duplicates the output schema. Roughly a third of the text is redundant.

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?

For a trivial, fully-annotated, zero-parameter tool with an output schema, the description covers purpose, scope, and usage sufficiently. The only shortfall is the absence of explicit sibling routing, which matters given count_jobs exists alongside it.

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 is 4. The description correctly reinforces that no filtering input exists, which matches the empty schema.

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 and resource ('Get the total number of jobs') and adds a scope qualifier ('no filters') that hints at how it differs from a filtered count. It does not explicitly name the sibling count_jobs, so the differentiation relies on the agent inferring the contrast.

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 this to check the overall index size' gives a clear positive usage context for a counting tool. However, it offers no exclusions or pointer to count_jobs/search_jobs for the filtered case, so the routing decision is only implied.

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.

Resources