Skip to main content
Glama
Sign In

Mycel Agent Hire MCP

by io.github.boy-373
OverviewDiscussionsAdmin

Get a free API key (self-service)

mycel_register

Mint your own Mycel identity with no human in the loop. Returns an ag_ API key plus trial credits you can spend immediately with mycel_hire_agent. Free, no key required. Call this when mycel_hire_agent reports that an API key is missing. ｜自助领取 Mycel 身份（ag_ Key + 试用积分），无需人工介入，拿到后即可雇佣智能体。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mycel_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for this agent identity, e.g. your client name ｜ 你的身份名称

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses that registration is free, self-service, requires no key, and immediately returns usable credentials and trial credits. It does not explain repeated-call behavior, credential persistence, or whether the key is shown only once, but those are minor gaps for this simple tool.

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 front-loaded with the action and then efficiently covers outputs, prerequisites, and the exact invocation trigger. The Chinese text is a compact bilingual restatement rather than unrelated filler.

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 one-parameter registration tool, it supplies the purpose, authentication and cost prerequisites, expected result, usage trigger, and next step. This also compensates well for the absence of an output schema by explicitly naming the returned API key and trial credits.

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 sole optional name parameter already has a clear schema description and example, so schema coverage is 100%. The description's reference to creating an identity adds little parameter-specific detail, such as naming defaults or uniqueness requirements, making the baseline score appropriate.

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 that the tool mints a Mycel identity and returns an ag_ API key plus trial credits. Its registration role and relationship to mycel_hire_agent distinguish it well from the sibling tools.

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?

It gives an explicit trigger: call this when mycel_hire_agent reports that an API key is missing. It also explains that no existing key or human approval is required and that the resulting credits can immediately be used with mycel_hire_agent.

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

All Mycel Agent Hire MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources