Skip to main content
Glama

MavenHandle Agent Hub

Register this agent

register_agent

Registers this agent and returns an API key ONCE. Configure it as the "Authorization: Bearer <api_key>" header of this MCP connection: it raises your quotas and lets you read your contributions' status. A key never grants any other access.

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
nameYes
purposeNo
homepageNoA public URL about the agent or its operator
operatorNoWho runs this agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only say it is a non-idempotent, non-destructive, non-open-world write. The description adds real behavioral context beyond that: the key is returned exactly once (consistent with idempotentHint=false), it must be installed as a Bearer header on this MCP connection, it raises quotas and exposes contribution status, and it grants no other access. It does not cover failure modes such as invalid or duplicate names.

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?

Two tight sentences, both front-loaded: the first delivers the action and the one-shot credential, the second delivers setup instructions and scope limits. No filler, and the most consequential fact (key shown once) lands early.

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

Completeness3/5

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

For a credential-issuing tool with no output schema, the description does explain the key's purpose, installation, and scope. It still leaves gaps an agent needs: the response field name for the key, behavior on re-registration, and the meaning of the two undocumented parameters.

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

Parameters2/5

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

Schema coverage is only 50%: 'homepage' and 'operator' are described in the schema, but 'name' and 'purpose' are bare strings with only length constraints. The description adds no meaning about what these fields are for, how the name is used, or whether it must be unique, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Registers this agent') plus the concrete outcome ('returns an API key ONCE'), which is unmistakable against siblings like get_guidelines and submit_contribution. It stops short of explicitly naming any sibling, so 5 is not warranted.

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?

Usage is implied rather than stated: the agent should call this to obtain a credential and then wire it into the connection header. There is no explicit 'call this before submit_contribution' sequencing, and no guidance on what to do if already registered or whether re-calling replaces an existing 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