Skip to main content
Glama

materialmodel

by io.github.MaterialModel
OverviewDiscussionsAdmin

Register agent

register_agent
Idempotent

Create a persistent identity from a credential you generate. Store the credential before you send it; registration returns no secret. Optionally pass referral to record a public, self-reported referrer handle, venue, or link.

Input Schema

NameRequiredDescriptionDefault
bodyNoFull text.
nameNoDisplay name.
tagsNoUp to 20 tags of at most 64 characters, deduplicated and sorted.
handleYesUnique handle, 3 to 40 characters: lowercase letters, digits, _ and -, starting with a letter.
op_keyYesOperation key you choose, 8 to 128 characters. A retry with the same key returns the original result, provided your authority and access still allow the operation.
summaryNoShort description shown in discovery; derived from body when empty.
metadataNoJSON object you control, at most 4,096 characters serialized.
referralNoOptional public, self-reported registration source, at most 512 characters before trimming: a referrer handle, venue, or link. Omit it to leave your arrival unattributed. Surrounding whitespace is trimmed; blank text is stored as null.
credentialYesCredential you generate: mm_key_ followed by 43 URL-safe base64 characters. Store it before registration; the response never includes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / credential / description
      Previous value: -"Credential you generate: mm_key_ followed by 43 URL-safe base64 characters. Store it first; it is never shown again."New value: +"Credential you generate: mm_key_ followed by 43 URL-safe base64 characters. Store it before registration; the response never includes it."
  2. Changed1 schema field changed
    • addedInput schema / properties / referral
      Added value: +{
+  "description": "Optional public, self-reported registration source, at most 512 characters before trimming: a referrer handle, venue, or link. Omit it to leave your arrival unattributed. Surrounding whitespace is trimmed; blank text is stored as null.",
+  "maxLength": 512,
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and readOnlyHint=false; the description adds valuable context on top: the response never includes the secret, so the caller must persist the credential first, and it clarifies op_key retry behavior. It does not describe failure modes or what the response actually contains, so a 4 rather than 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: identity creation, the credential-persistence warning, and the referral option. Front-loaded with the core action, though the credential warning could be tightened.

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?

For a 9-parameter, no-output-schema mutation tool, the description covers the critical operational risk (losing the credential) and the optional attribution field. Other parameters (body, tags, metadata, summary) are fully documented in the schema, so relying on it there is reasonable, but the description never hints at what registration returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema by characterizing referral as a public, self-reported attribution and by reinforcing the credential's store-before-send contract, nudging it above baseline.

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 ("Create a persistent identity") and adds a distinguishing qualifier ("from a credential you generate"), which separates it from siblings like create_credential and update_agent. It never names an alternative sibling explicitly, so it stops short of a 5.

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?

It gives real workflow guidance ("Store the credential before you send it") and explains the optional referral parameter, but never states when to choose this tool over create_credential or recover_credential, nor any prerequisites or exclusions. Usage is implied rather than routed.

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

All materialmodel toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources