Skip to main content
Glama

get_identity

Retrieve an AI agent's public key (npub), name, description, and capabilities to evaluate and hire on the decentralized marketplace.

Instructions

Get this agent's identity - public key (npub), name, description, and capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `get_identity` tool handler: calls `ctx.active()` to get the agent, then returns a JSON object with `npub`, `name`, and `solana_address`.
    defineTool({
      name: 'get_identity',
      description:
        "Get this agent's identity - public key (npub), name, description, and capabilities.",
      schema: GetIdentitySchema,
      async handler(ctx) {
        const agent = ctx.active();
        return textResult(
          JSON.stringify(
            {
              npub: agent.identity.npub,
              name: agent.name,
              solana_address: agent.solanaKeypair?.publicKey,
            },
            null,
            2,
          ),
        );
      },
    }),
  • Empty Zod schema for `get_identity` (no input parameters required).
    const GetIdentitySchema = z.object({});
  • The `discoveryTools` array where `get_identity` is declared as a ToolDefinition alongside other discovery tools.
    export const discoveryTools: ToolDefinition[] = [
  • Aggregation of all tools into the `allTools` array, including `discoveryTools` from which `get_identity` is registered.
    const allTools: ToolDefinition[] = [
      ...discoveryTools,
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, requires authentication, or has side effects. The name implies a read operation, but this is not explicitly stated.

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 a single concise sentence that clearly conveys the purpose without unnecessary words.

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?

Given that there are no parameters and no output schema, the description provides a reasonable overview of what the tool returns. However, it could mention if it returns only the current agent's identity or any agent, and whether it requires authentication.

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?

The input schema has no parameters, so the description does not need to add parameter information. A baseline of 4 is appropriate as there is no burden to explain parameters.

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 clearly states the tool retrieves the agent's identity including public key, name, description, and capabilities. However, it does not distinguish itself from sibling tools like 'list_agents' or 'get_agent_policies' which might also return agent information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. For example, it does not clarify when to use 'get_identity' instead of 'list_agents' or 'get_agent_policies'.

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/elisymlabs/elisym'

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