Skip to main content
Glama
Sign In
EasySourceFlow

EasySourceFlow

by john-ops-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

easysourceflow_get_batch

Read-onlyIdempotent

Retrieve the current status and per-link job details of a batch using its unique batch ID.

Instructions

Get status and per-link jobs for a batch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "batch_id": "<batch_id>"
    },
    "name": "easysourceflow_get_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesBatch ID returned by easysourceflow_submit_batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool retrieves status and per-link jobs, which is consistent and provides some behavioral context beyond annotations, but does not elaborate on response format or side effects.

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 description is a single concise sentence that is front-loaded with the core action. It could be expanded with usage context without becoming overly long.

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?

Given the simple input schema (one parameter with full description) and annotations covering safety, the description adequately conveys the tool's purpose. However, the lack of output schema and any explanation of the return format or typical usage patterns leaves some context missing.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter (batch_id), and the description does not add any additional meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 that the tool gets 'status and per-link jobs for a batch'. The verb 'Get' is specific, and the resource 'batch' distinguishes it from sibling tools like easysourceflow_get_job (single job) and easysourceflow_list_recent_jobs (list of recent jobs).

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_job, list_recent_jobs) or any prerequisites beyond the batch_id parameter.

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