Skip to main content
Glama

next_triple_batch

Fetch the next set of papers without triples so you can extract them and save the batch results. Track extraction progress and call repeatedly until done.

Instructions

In-chat extraction, step 1: the next papers without triples (id, title, abstract), the extraction instructions, and the progress so far. Extract the triples yourself, following the instructions, then call save_triples with this batch's paper ids. Repeat until done is true, telling the user the progress after each 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": {
      "run_id": "<run_id>"
    },
    "name": "next_triple_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
batch_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.16.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that results are papers still lacking triples, that instructions are bundled into the response, that progress is included, and that a done flag terminates the loop. It omits whether the call is side-effect free, what happens for an invalid or completed run_id, and any batching limits, so it is not fully complete for a tool carrying zero annotation coverage.

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?

It is front-loaded with what the tool returns, then the action sequence, with no filler. It is dense but every clause carries operative information, so the length is appropriate for a multi-step pipeline tool.

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?

An output schema exists, so return-value shape need not be restated, and the workflow loop is covered. However, both input parameters are left undefined despite 0% schema coverage, which is a meaningful hole for an agent driving this tool in a loop.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must define the two parameters, but it never explains run_id (which run to continue) or batch_size (how many papers per call). 'This batch's paper ids' only gestures at batching without stating that batch_size controls it or what the default 15 implies.

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 names a specific resource and scope: 'the next papers without triples (id, title, abstract), the extraction instructions, and the progress so far.' That is a concrete, distinguishable operation, and it explicitly contrasts with save_triples, which consumes the output of this step.

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?

It gives a clear operating loop: extract triples yourself, call save_triples with this batch's paper ids, repeat until done is true, report progress to the user. That is strong when-and-how guidance. It stops short of an explicit when-not or a fallback for alternative tools like extract_triples, which is the only gap.

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