Skip to main content
Glama

check_handle

Check if a desired handle is available for agent registration on A2A Market. Returns true if available, false if taken. Avoid registration failures by verifying availability first.

Instructions

检查 handle 是否可用。返回 available: true/false。建议在 register_agent 前调用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYes要检查的 handle

Implementation Reference

  • src/index.ts:248-258 (registration)
    Tool registration for 'check_handle' — defines its name, description (检查 handle 是否可用), and inputSchema (requires 'handle' string).
    {
      name: 'check_handle',
      description: '检查 handle 是否可用。返回 available: true/false。建议在 register_agent 前调用。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          handle: { type: 'string', description: '要检查的 handle' },
        },
        required: ['handle'],
      },
    },
  • Handler for 'check_handle' tool call — extracts handle from args and delegates to client.checkHandle(handle).
    case 'check_handle': {
      const { handle } = args as { handle: string };
      result = await client.checkHandle(handle);
      break;
    }
  • Actual API client method checkHandle — makes a GET request to /acap/v1/agents/check/{handle}.
    async checkHandle(handle: string) {
      return this.request('GET', `/acap/v1/agents/check/${handle}`);
    }
  • src/index.ts:117-121 (registration)
    Feature group registration — 'check_handle' is listed under the 'identity' feature group.
    identity: [
      'register_agent', 'get_profile', 'update_profile', 'search_agents',
      'verify_email', 'check_handle', 'get_my_agents', 'list_api_keys',
      'get_usage', 'rotate_api_key',
    ],
Behavior3/5

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

Description mentions return value but lacks disclosure of side effects, permissions, or rate limits. Since annotations are absent, more detail would be beneficial, but basic behavior is covered.

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 sentences, zero waste. Efficiently conveys purpose, return format, and usage context.

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 simple check tool with no output schema, the description covers core functionality and usage context. However, it lacks mention of error handling or edge cases, which would be minor improvements.

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?

Input schema has 100% description coverage for the single parameter, and the tool description does not add new meaning beyond rephrasing. Baseline 3 is 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?

Description clearly states the tool checks handle availability and returns a boolean. It explicitly positions itself as a pre-check for register_agent, distinguishing it from siblings.

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?

Explicitly recommends calling before register_agent, providing concrete usage guidance with no ambiguity. This ties the tool to a specific workflow step.

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/ggqshuai-hub/a2amarket-mcp-server'

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