Skip to main content
Glama
Sign In
EasySourceFlow

EasySourceFlow

by john-ops-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

easysourceflow_list_recent_jobs

Read-onlyIdempotent

List recent job entries from the SQLite store, with optional filtering by status and limit control.

Instructions

List recent EasySourceFlow jobs from the local SQLite store.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoOptional job status filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds minimal extra behavioral transparency. It confirms the tool reads local data but does not disclose details like pagination, order, or whether jobs are sorted by time.

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?

Single sentence of 10 words, perfectly concise. No fluff, immediately conveys core function.

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?

The description is adequate for a simple read-only list tool with two optional parameters and no output schema. However, it could be more complete by mentioning the parameters (e.g., 'list recent jobs, optionally filtered by status' and that limit controls count). The absence of output schema means the description could hint at the return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention either parameter (limit, status). With schema description coverage only 50% (status has doc, limit has none), the description could compensate but does not. The agent gets no added meaning beyond the schema's minimal definitions.

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 states the action (list), the resource (recent EasySourceFlow jobs), and the source (local SQLite store). It clearly distinguishes the tool's purpose from siblings like easysourceflow_get_job (which retrieves a single job) and easysourceflow_search_outputs (which searches outputs), though it could explicitly note that it queries local storage.

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?

No guidance on when to use this tool vs alternatives. For example, it does not explain when to use this over easysourceflow_get_job or easysourceflow_search_outputs, nor does it mention prerequisites or limitations.

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