Skip to main content
Glama
deenesjakoruzh
avivshafir

trykittai-mcp-server

by avivshafir
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_jobs

Retrieve and display available jobs from the trykittai MCP server for monitoring and management purposes.

Instructions

List jobs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:79-86 (handler)
    The main handler function for the 'list_jobs' tool. It is registered via the @mcp.tool() decorator and implements the tool logic by sending a GET request to the /job endpoint of the TryKitt API and returning the JSON response.
    @mcp.tool()
async def list_jobs() -> Dict:
    """
    List jobs
    """
    response = await http_client.get(f"/job")
    return response.json()

Tool Definition Quality

D1.8/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. 'List jobs' doesn't indicate whether this is a read-only operation, whether it requires authentication, what format results are returned in, if there are rate limits, or any other behavioral characteristics. The description fails to provide any operational context beyond the basic action.

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

Conciseness2/5

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

While technically concise with just two words, this description represents under-specification rather than effective brevity. The single phrase 'List jobs' fails to provide necessary context that would help an agent understand when and how to use this tool. Conciseness should not come at the expense of clarity and completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description 'List jobs' is completely inadequate. It doesn't explain what constitutes a 'job' in this context, what information is returned, whether results are paginated, or any other operational details. The description fails to provide the minimal context needed for effective tool invocation.

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 has zero parameters, and the input schema has 100% description coverage (though empty). With no parameters to document, the description doesn't need to compensate for schema gaps. The baseline for zero-parameter tools is 4, as there's no parameter semantics burden on the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List jobs' is a tautology that merely restates the tool name without adding meaningful context. It specifies the verb ('list') and resource ('jobs'), but provides no differentiation from sibling tools like 'get_job_status' or additional scope information. This minimal description fails to clarify what type of jobs are being listed or under what conditions.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives like 'get_job_status' or other sibling tools. There's no mention of appropriate contexts, prerequisites, or exclusions. Users must infer usage patterns from the tool name alone, which is insufficient for effective tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/avivshafir/trykittai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server