AgentStamp

create_team

Create a team for multi-agent trust scoring; owner auto-added as first member. Use REST API with wallet signature for production.

Instructions

Create a new agent team for multi-agent trust scoring. Owner is auto-added as first member. Note: for production use, prefer the REST API (POST /api/v1/teams) which requires wallet signature verification.

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": {
      "name": "<name>",
      "wallet_address": "<wallet_address>"
    },
    "name": "create_team"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Team name (max 100 characters)
`description`	No	Team description (max 500 characters)
`wallet_address`	Yes	Wallet address of the team owner (must be a registered agent)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0May 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the owner is auto-added as first member, a behavioral trait. However, it does not mention auth requirements (beyond the REST API note), error conditions, or return values, leaving gaps. The production note is more of a recommendation than a behavior, so the actual behavioral disclosure is limited.

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?

The description is two sentences, front-loads the purpose, and provides a useful side note about the owner and a production alternative without any fluff. Every sentence earns its place.

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?

The tool has no output schema, and the description does not explain return values or error behavior, but it covers purpose, a key side effect (owner auto-added), and a usage recommendation. This is reasonably complete for a simple create operation, though it could mention response details for 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?

The schema covers 100% of parameters with descriptions. The description adds the note that the owner is auto-added, which provides slight context to the wallet_address parameter (i.e., the owner need not be listed as a member), but it doesn't significantly go beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 uses a specific verb ('Create') and resource ('agent team') and adds context ('for multi-agent trust scoring'), clearly distinguishing it from sibling tools like team_trust_check or browse_agents. It fully states what the tool does with no ambiguity.

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

Usage Guidelines5/5

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

The description explicitly states that for production use, the REST API (POST /api/v1/teams) is preferred because it requires wallet signature verification. This provides a clear alternative and when-to-use guidance, which is exactly what a good usage guideline should do.

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