get_job_statistics
Get aggregate statistics (active jobs, new-this-week/month, top sources, salary ranges) for nomado24's remote-jobs board. No input required.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Nomado24 Remote Jobs
by de.nomado24
TDQS
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool performs a read-only operation (getting statistics) and lists the specific metrics it returns. It also states 'No input required,' setting clear expectations. There are no hidden side effects or prerequisites mentioned, but given the simplicity of the tool, this is adequate.
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?
The description is a single, concise sentence that front-loads the core purpose and includes only necessary detail. There is no waste or redundancy.
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 tool with zero parameters and no output schema, the description is fully complete. It specifies the data returned, the domain (nomado24's remote-jobs board), and invocation requirements (no input). No additional context is needed for an agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty, and the description explicitly states 'No input required,' leaving no ambiguity about invocation. Given zero parameters, the description provides complete clarity beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('aggregate statistics ... for nomado24's remote-jobs board'). It enumerates the types of statistics (active jobs, new-this-week/month, top sources, salary ranges), which distinguishes it from the sibling tool search_jobs, presumably a job search tool.
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?
The description indicates the tool's usage context (aggregate statistics for a remote-jobs board) and explicitly states 'No input required,' clarifying that no parameters are needed. However, it does not explicitly mention when to use this tool instead of search_jobs or provide exclusions, though the purpose makes the distinction clear.
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.
TDQS
A4.7/5.0
Disambiguation5/5
The three tools are completely distinct: get_job fetches a single job by ID, search_jobs performs filtered/queries searches, and get_job_statistics returns aggregate board metrics. There is no functional overlap; an agent can unambiguously choose the right tool for each task.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: get_job, get_job_statistics, and search_jobs. They are all lowercase with underscores, and while search_jobs uses 'search' instead of 'get', it still adheres to the same grammatical structure and style, making the set predictable.
Tool Count5/5
With only three tools, the server is tightly scoped to the core read-only operations of a job board: retrieving a specific posting, searching with flexible filters, and obtaining high-level statistics. Each tool serves a clear, non-redundant purpose, and the count is appropriate for the domain.
Completeness5/5
For a read-only remote jobs board, the surface is complete: search covers discovery with rich filters and paging, get_job provides full details for a specific posting, and get_job_statistics gives aggregate insights. There are no missing CRUD/lifecycle operations because the board is deliberately read-only, and the tool set covers all necessary actions.