Skip to main content
Glama
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

curator_research_write

Idempotent

Secure and persist public web evidence gathered during research. This function transfers bounded data from specialized agents to the parent for final archival or use.

Instructions

Persist bounded public web evidence to a parent-authorized handoff.

Only a spawned curator_researcher child carrying the matching pass ID may call this tool. The parent chooses the filename from pass and batch metadata; callers cannot select a destination or hand evidence to another batch. The web-only child receives no local inventory, memory, or repository access.

Input Schema

NameRequiredDescriptionDefault
contentNo
pass_idNo
batch_indexNo
batch_totalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.21.0
    • addedInput schema / properties / content / default
      Added value: +""
    • addedInput schema / properties / pass_id / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "pass_id",
-  "content"
-]
  2. Addedv0.18.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false), and the description adds real value beyond that: authorization model (parent-authorized handoff), destination control (parent picks filename), and caller sandboxing (no local inventory/memory/repo access). Missing only what 'bounded' enforces (size/content limits).

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?

Four tight sentences, purpose front-loaded ahead of the authorization and sandboxing constraints. No filler; each sentence adds a distinct constraint. Slightly dense wording ('parent-authorized handoff') but efficient.

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?

Output schema exists, so return values needn't be described; annotations cover safety; the description covers authorization, destination control, and caller limitations. The only gap is concrete guidance on 'bounded' evidence (size/content expectations) and eligibility failure behavior.

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 compensate. It explains pass_id (matching pass), batch metadata (batch_index/batch_total drive parent's filename choice), and implies content carries the evidence, but it doesn't clarify content format, size bounds, or how batch_index/batch_total relate to a single call. Partial compensation for a 4-param tool.

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?

States a specific verb ('Persist') and resource ('bounded public web evidence to a parent-authorized handoff'), which is concrete enough for an agent to know the operation. It doesn't name a sibling alternative (e.g., curator_report_write), but the curator_researcher/child framing disambiguates it from general write tools.

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?

Explicitly states the calling condition: only a spawned curator_researcher child with the matching pass ID may call it, and callers cannot choose a destination or redirect evidence. That's strong when-to-use guidance, though it doesn't name an alternative tool or state what to do if not eligible.

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