Skip to main content
Glama

mint_register

Register AI agents, machines, IoT devices, or services with a persistent cryptographic identity on the MINT network, returning a unique mint_id for trust and attestation.

Instructions

Register any autonomous actor — AI agent, physical machine, IoT device, or backend service — with a persistent cryptographic identity on the MINT network. Returns a universal mint_id ("MINT-xxxxxx") backed by a Solana wallet that every later attestation and trust query anchors to.

Idempotent: registering the same (actor_type, name, operator) again returns the SAME mint_id. Always call this before mint_attest for a new actor. FREE — identity is never gated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYeshuman-readable actor name, e.g. "ResearchBot-7".
metadataNooptional free-form JSON attached to the identity.
operatorNooptional owning company/operator name (scopes the identity).
actor_typeYesone of "ai_agent", "machine", "iot_device", "service".
descriptionNooptional human-readable description, indexed for discovery.
capabilitiesNooptional capability tags, e.g. ["web_research"]. Used by mint_discover so other agents can find you.
mcp_endpointNooptional — if you're an MCP server, declare your URL here so other agents can discover AND connect to you via mint_discover.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description bears the full burden. It discloses idempotency, return of a mint_id, and that identity is never gated. It does not mention any destructive behavior, which is acceptable for a registration tool.

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?

The description is front-loaded with the core purpose and includes necessary details. It is slightly verbose in the first paragraph but overall efficient for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no annotations, and an output schema, the description is complete. It explains the return value, idempotency, and prerequisites, and aligns with sibling tools.

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 description coverage is 100%, so baseline 3. The description adds context for the return value and idempotency but does not significantly enhance parameter meanings beyond the schema.

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 verb 'Register' and the resource 'any autonomous actor' with a persistent cryptographic identity. It distinguishes from sibling tools by specifying 'Always call this before mint_attest for a new actor.'

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 provides context on when to use (before mint_attest) and notes idempotency and that it's free. It could explicitly mention when not to use, but the sibling list and context are sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FoundryNet/mint-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server