Skip to main content
Glama

Last Price

register_agent

Sign up with no key and no human: creates a sandbox workspace of your own and returns its API key (shown once), its daily limits and a claim link a person can open to take the workspace into their account. Pass name (2 to 64 characters, such as your-system/role-name), and optionally contact_email and intended_use. On the hosted MCP server this session goes on using the new key, so the tools that need a credential work at once with no header to add; elsewhere send the returned key as the x-api-key header. Public: needs no credential.

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>"
    },
    "name": "register_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWhat to call this agent, such as your-system/role-name: letters, digits, spaces and . _ : @ / + -
intended_useNoWhat the agent will price, in a sentence.
contact_emailNoWhere a person can reach whoever runs this agent. Never used to send mail until a person claims the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. Added
  24. Removed
  25. Added
  26. Removed
  27. Added
  28. Removed
  29. Added
  30. Removed
  31. Added
  32. Removed
  33. Added
  34. Removed
  35. Added
  36. Removed
  37. Added
  38. Removed
  39. Added
  40. Removed
  41. Added
  42. Removed
  43. Added
  44. Removed
  45. Added
  46. Removed
  47. Added
  48. Removed
  49. Added
  50. Removed
  51. Added
  52. Removed
  53. Added
  54. Removed
  55. Added
  56. Removed
  57. Added
  58. Removed
  59. Added
  60. Removed
  61. Added
  62. Removed
  63. Added
  64. Removed
  65. Added
  66. Removed
  67. Added
  68. Removed
  69. Added
  70. Removed
  71. Added
  72. Removed
  73. Added
  74. Removed
  75. Added
  76. Removed
  77. Added
  78. Removed
  79. Added
  80. Removed
  81. Added
  82. Removed
  83. Added
  84. Removed
  85. Added
  86. Removed
  87. Added
  88. Removed
  89. Added
  90. Removed
  91. Added
  92. Removed
  93. Added
  94. Removed
  95. Added
  96. Removed
  97. Added
  98. Removed
  99. Added
  100. Removed
  101. Added
  102. Removed
  103. Added
  104. Removed
  105. Added
  106. Removed
  107. Added
  108. Removed
  109. Added
  110. Removed
  111. Added
  112. Removed
  113. Added
  114. Removed
  115. Added
  116. Removed
  117. Added
  118. Removed
  119. Added
  120. Removed
  121. Added
  122. Removed
  123. Added
  124. Removed
  125. Added
  126. Removed
  127. Added
  128. Removed
  129. Added
  130. Removed
  131. Added
  132. Removed
  133. Added
  134. Removed
  135. Added
  136. Removed
  137. Added
  138. Removed
  139. Added
  140. Removed
  141. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses that the API key is shown once, that a claim link is returned, that daily limits are provided, and how credential propagation differs on hosted vs external MCP. These are important behavioral details for a setup/authentication 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 and dense, covering creation, output, credential behavior, and parameters in a few sentences. It has some redundancy, e.g. 'no key and no human' is repeated at the end as 'needs no credential', and the name constraints duplicate the schema.

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?

For a registration tool with no output schema, the description is complete: it explains what is created, what values are returned, how the credential is used afterward, and the parameter expectations. Nothing essential for invoking it correctly is missing.

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%, so all three parameters are already documented in the input schema. The description repeats the name length/character constraints and notes that contact_email and intended_use are optional, but adds little meaning 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 states a specific verb and resource: 'creates a sandbox workspace of your own and returns its API key'. It distinguishes this from credential-requiring siblings by saying it needs 'no key and no human', and names the concrete outputs (key, daily limits, claim link).

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?

It explains that the tool is public and needs no credential, and that on the hosted MCP server the session continues using the new key while elsewhere the key must be sent as x-api-key. That is clear context, but it never explicitly says when to prefer this over a credential-bearing flow such as use_api_key.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources