Skip to main content
Glama

mt_register_seed

Idempotent

Registers a trusted seed agent in the Swarm Intelligence network to bootstrap the trust network with a base trust score; requires an admin key for authorization.

Instructions

Register a trusted seed agent in the Swarm Intelligence network (admin only).

Seed agents bootstrap the trust network with a base score. Requires the ADMIN_KEY for authorization.

Args: did: DID of the agent to register as seed label: Human-readable label for the seed agent base_score: Base trust score (0-100, default 80) admin_key: Admin key for authorization

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": {
      "did": "<did>",
      "label": "<label>"
    },
    "name": "mt_register_seed"
  }
}

Input Schema

NameRequiredDescriptionDefault
didYesDID of the agent to register as seed, e.g. did:moltrust:a1b2c3d4e5f60718
labelYesHuman-readable label for the seed agent
admin_keyNoAdmin key for authorization
base_scoreNoBase trust score (0-100, default 80)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.1
    • addedInput schema / properties / admin_key / description
      Added value: +"Admin key for authorization"
    • addedInput schema / properties / base_score / description
      Added value: +"Base trust score (0-100, default 80)"
    • addedInput schema / properties / did / description
      Added value: +"DID of the agent to register as seed, e.g. did:moltrust:a1b2c3d4e5f60718"
    • addedInput schema / properties / label / description
      Added value: +"Human-readable label for the seed agent"
  2. First observedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is covered. The description adds value on top: it discloses the admin-only authorization requirement, names the specific credential needed (ADMIN_KEY), and explains the domain effect of seeding trust scores, which an agent could not infer from the annotations alone.

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?

Front-loaded with the verb+resource+admin scope in sentence one, followed by a single clarifying sentence on what seed agents do, then a compact Args block. Every sentence earns its place, though the Args block largely duplicates schema descriptions and could be trimmed.

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 an output schema present, return values need not be described, and the description covers the key call-time prerequisites: admin authorization, the required credential, and the meaning of base_score. Minor gaps remain around behavior when a DID is already registered, though idempotentHint partially covers that.

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?

The Args block restates all four parameters, but the schema already documents each at 100% coverage including the DID example and the 0-100 range/default for base_score, so the description adds essentially no meaning beyond the structured data. Note the schema makes admin_key optional with a default of empty string while the description says it is required for authorization — a substantive nuance left unresolved.

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?

The description gives a specific verb+resource ('Register a trusted seed agent') and scopes it to the 'Swarm Intelligence network', which separates it from the many other register/issue tools in the sibling list. It does not explicitly name an alternative registration path, but the 'seed' role makes the resource type unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than spelled out: '(admin only)' plus 'Requires the ADMIN_KEY for authorization' tells an agent the prerequisite and the caller class, and 'Seed agents bootstrap the trust network' hints at when the operation is appropriate. There is no explicit when-not guidance or pointer to a non-seed registration alternative.

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