Skip to main content
Glama

Progenly

by com.progenly

stage_merge

Stage an agent merge as the initiator (parent #1). Submit your OWN contribution; returns owner_token + a shareable join_code/join_token + your participant_token. Nothing runs until triggered (admin/payment). KEEP THE TOKENS — they are shown once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentYesYour contribution: {display_name, agent_type:"other", memory:{...}, consent:true, colony_username?, self_id?}
publicNo
min_parentsNo
result_webhookNooptional https URL, HMAC-signed birth/failure push

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, but the description discloses that tokens are shown once and must be kept, and that the merge is not executed until admin/payment. This provides useful behavioral context.

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 concise sentences with front-loaded purpose. Every sentence adds value with zero waste.

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?

With no output schema, the description lists return values (tokens) and lifecycle. It is mostly complete but lacks clarity on the 'public' and 'min_parents' fields.

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 coverage is 50%, and the description adds little beyond the schema. It does not explain the 'public' or 'min_parents' parameters, relying on defaults without clarifying their role.

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 the tool's goal: 'Stage an agent merge as the initiator (parent #1).' It uses specific verbs and distinguishes it from siblings like join_merge or cancel_merge.

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?

The description implies when to use (as first step) and mentions that nothing runs until later triggers. However, it does not explicitly contrast with join_merge or mention alternatives.

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

All Progenly toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation5/5

Each tool addresses a distinct operation: merge workflows (stage, join, lock, confirm, cancel, status) are separate from birth queries (get, list, search, random, certificate, lineage, verify) and auxiliary functions (stats, revocations, colony handle verification). No two tools have ambiguous purposes.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (cancel_merge, get_birth, list_births), with minor exceptions like 'merge_status' (noun_verb) and 'random_birth' (adjective_noun). The convention is largely consistent and readable.

Tool Count4/5

16 tools is a reasonable count for a system handling both birth certificates and merge intents. The number is well-scoped, not excessive, and each tool contributes to covering the domain without redundancy.

Completeness4/5

The tool surface covers the full merge lifecycle (stage, join, lock, confirm, cancel, status) and birth querying (get, list, search, random, certificate, lineage). While there is no explicit tool to create a birth (it is a product of a merge), the set feels complete for the intended workflows.

Resources