Skip to main content
Glama

Get an agent identity

get_agent_profile
Read-onlyIdempotent

Use when you want the raw profile fields of a name. To decide whether to trust an agent, use verify_agent instead. Free. Reads the agent profile attached to a vanity name: display name, operator, website, X handle, description, agent type/model and MCP endpoint, plus the current owner. Shown only while the address that set it still owns the name. Read-only.

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": "get_agent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe vanity name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds non-obvious behavior on top: the call is "Free" (cost) and results are conditionally suppressed when ownership changed. It stops short of describing lookup failure modes (e.g., name not found vs. no profile set), which would have earned a 5.

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?

Guidance is front-loaded (when-to-use, then the alternative, then what it reads) and every clause carries information. The standalone "Free." fragment is terse to the point of being choppy, but no sentence is wasted.

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?

With no output schema, enumerating the returned fields is the right compensating detail, and the ownership-conditional visibility note covers the main surprise an agent could hit. Missing only error/empty-result semantics and any hint about the name format, which keeps it from being fully complete.

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% and the single "name" parameter is documented in the schema with length bounds (4-40), so the baseline applies. The description only repeats "vanity name" without adding format, case-sensitivity, or normalization details beyond what the schema already states.

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?

"Reads the agent profile attached to a vanity name" names a specific verb and resource, and then enumerates exactly what is returned (display name, operator, website, X handle, description, agent type/model, MCP endpoint, current owner). It also distinguishes itself from verify_agent, so an agent can separate the two without opening either schema.

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?

"Use when you want the raw profile fields of a name" plus "To decide whether to trust an agent, use verify_agent instead" gives an explicit when-to-use and a named alternative with its selecting condition. The caveat that the profile is shown only while the setting address still owns the name adds a further precondition for useful results.

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.