Skip to main content
Glama

dispatch_mapreduce_text

Submits text chunks to the grid for entity and relationship extraction across idle workers, returning merged entities, triples, counts, and failures; use wait=false for a job ID.

Instructions

Submit text chunks to the grid for entity/relationship extraction (one model call per chunk, spread across idle workers). With wait=true (default) blocks until done, reporting progress, and returns counts, elapsed time, failed chunks, the merged top entities and up to 200 [subject, RELATION, object] triples. With wait=false returns the job_id at once. required_tier: 1 any worker, 2 workers with 8-24GB free RAM, 3 the largest machines.

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": {
      "job_name": "<job_name>",
      "chunks": "<chunks>"
    },
    "name": "dispatch_mapreduce_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
chunksYes
job_nameYes
timeout_sNo
required_tierNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, destructive=false; the description adds substantial context beyond that — blocking vs. non-blocking behavior, progress reporting, that failed chunks are reported, elapsed time, and resource-tier gating for workers. These are the operational traits an agent needs before firing off a potentially long distributed job.

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?

Three dense sentences, no filler, with the core action and its execution model front-loaded before the result-shape and tier details. Every clause conveys information the agent cannot get from the structured fields.

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

Completeness4/5

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

For a moderate-complexity distributed dispatch tool with an output schema, the description covers invocation semantics, blocking behavior, and result contents adequately. Gaps remain around timeout behavior, job_name semantics, and how to follow up on a non-blocking job (presumably via grid_status), which keeps it from full completeness.

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 0%, so the description must carry the burden; it explains wait and required_tier well (including what each tier means in RAM terms) and implies chunks are processed one-per-model-call. However, job_name (uniqueness, collisions, reuse) and timeout_s (what happens at expiry — partial results, failure, or silent truncation) are never explained in either schema or description.

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?

States a specific verb and resource — submitting text chunks to the grid for entity/relationship extraction — plus the execution model (one model call per chunk, spread across idle workers). This distinguishes it clearly from siblings like grid_status (monitoring) and query_local_graph (querying), so an agent can select it without opening the schema.

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?

Gives concrete mode-selection guidance: wait=true blocks and returns results, wait=false returns a job_id immediately, and required_tier maps each tier value to a worker class. It does not name alternatives or exclusions (e.g., when to prefer ingest_directory_to_graph for files already on disk versus submitting chunks directly), so it stops short of full routing guidance.

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