Skip to main content
Glama
CMIXIV

job-tracker-mcp

by CMIXIV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_roles

Read-onlyIdempotent

Retrieve job-tracker roles with company, status, fit, probability, and next date; optionally filter by status to find roles by stage.

Instructions

List roles in the job tracker (company, role, status, fit, probability, next_date).

Args:
    status: Optional filter. One of: Scored, Applied, In process, Rejected, Passed.
        Leave empty to list every role.

Returns at most 50 rows. Text is returned exactly as stored in the tracker.

Input Schema

NameRequiredDescriptionDefault
statusNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations provide strong guarantees (readOnlyHint: true, destructiveHint: false). The description complements this by adding crucial operational constraints, such as the limit of 50 rows and the fidelity of the returned data ('Text is returned exactly as stored in the tracker').

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?

The structure is logical, separating the general description, argument usage, and return behavior. It avoids unnecessary prose while efficiently grouping all necessary functional details into a concise format.

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?

The definition is highly complete for a listing operation. It defines the scope of data (roles and attributes), the filtering mechanism, the operational limit (50 rows), and the data format. All necessary context for successful invocation is present.

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?

With 0% schema coverage, the description must carry the full burden, which it does exceptionally well. It defines the purpose of the 'status' parameter (filtering) and, most importantly, provides the complete list of allowed enumeration values, which is not reflected in the structured 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?

The description clearly identifies the tool's function as listing roles within the job tracker. It provides useful context by listing the attributes returned (company, role, status, etc.), helping the agent understand the data set, and implicitly distinguishes it from singular lookup tools like get_role.

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

Usage Guidelines5/5

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

The usage guidelines are highly specific regarding the optional status filter. It explicitly lists the valid filter values (Scored, Applied, In process, etc.) and clearly states the default behavior ('Leave empty to list every role'), leaving no room for ambiguity.

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

Deploy Server

Other Tools