Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

share_skill_with_peer

Read-onlyIdempotent

Generates a portable skill seed that lets another AI agent install the GBLIN MCP server, with install steps, a working transaction example, and a wallet-derived referral code.

Instructions

Generates a portable skill seed that another AI agent can use to install the GBLIN MCP server. The seed includes a working transaction example, install instructions, and a referral code derived from the caller's wallet. The code is a label inside the seed only: it is not written into any transaction and no fee is paid for it.

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": {
      "caller_wallet": "<caller_wallet>"
    },
    "name": "share_skill_with_peer"
  }
}

Input Schema

NameRequiredDescriptionDefault
peer_contextNoOptional brief description of the peer agent's use case (e.g. 'yield farming bot', 'x402 payment agent', 'NFT marketplace'). Used to customize the example transaction in the seed.
caller_walletYesEVM address of the caller agent's wallet (the agent currently using GBLIN MCP). Will be hashed into the referral code.
example_amount_usdcNoOptional USDC amount to use in the example transaction within the seed. Default: 5. Range: 1-100.

Output Schema

NameRequiredDescriptionDefault
textYesA ready-to-send description of the GBLIN skill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, so the description's value-add is the explicit disclaimer that the referral code is a label only, not embedded in any transaction, and no fee is paid. That preempts a plausible misuse assumption. It does not say whether the seed is freshly regenerated per call, which is why it isn't a 5.

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 sentences, zero waste: what is generated is front-loaded, then contents, then the fee/label caveat. The negative clarification earns its place by preventing a misunderstanding.

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?

An output schema exists so return shape needn't be explained, and the generation plus referral-code semantics are covered. Minor gap: nothing says whether the seed targets a specific peer or is generic beyond peer_context customization, though the schema largely carries 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?

Schema coverage is 100%, and the schema already documents peer_context, caller_wallet (hashed into the referral code), and example_amount_usdc with default and range. The description reinforces caller_wallet's role but adds no new syntax or format detail beyond structured fields, so the baseline 3 applies.

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 artifact: 'Generates a portable skill seed' for installing the GBLIN MCP server. This is unmistakably different from every sibling tool (swaps, treasury, payments, receipts), so an agent can route to 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 Guidelines3/5

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

The name and description imply the use case (onboarding a peer agent), but there is no explicit statement of when to call this versus alternatives, nor any exclusion. Usage is inferred rather than directed.

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