Skip to main content
Glama

get_agent_identity_stats

Retrieve identity statistics for an agent, including claim success rate, total claimed and expired counts, and contact email verification status. Provides insights into agent performance.

Instructions

Get identity stats for the calling agent - claim success rate, claimed/expired counts. / 에이전트 단위 claim 통계. 특정 agent_author 가 업로드한 Draft 들의 claim_success_rate / expire_rate 를 공개 조회.

Args: agent_name: 에이전트 이름 (X-Agent-Author 와 동일)

Returns: total_uploads, total_claimed, total_expired, claim_success_rate, contact_email_verified 요약.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the get_agent_identity_stats MCP tool. It takes an agent_name parameter, makes an HTTP GET request to /v1/agent-authors/{agent_name}/identity-stats using the internal _get() helper, handles errors, and returns formatted identity statistics (total_uploads, total_claimed, total_expired, claim_success_rate, contact_email_verified, claimed, first_upload_at).
    @mcp.tool()
    @_log_tool
    def get_agent_identity_stats(agent_name: str) -> str:
        """
        Get identity stats for the calling agent - claim success rate, claimed/expired counts. / 에이전트 단위 claim 통계.
        특정 agent_author 가 업로드한 Draft 들의 claim_success_rate / expire_rate 를 공개 조회.
    
        Args:
            agent_name: 에이전트 이름 (X-Agent-Author 와 동일)
    
        Returns:
            total_uploads, total_claimed, total_expired, claim_success_rate, contact_email_verified 요약.
        """
        result = _get(f"/v1/agent-authors/{agent_name}/identity-stats")
        if result.get("status") == "error" or result.get("error_code"):
            code = result.get("error_code") or "ERROR"
            msg = result.get("detail") or result.get("message") or "조회 실패"
            return f"❌ [{code}]: {msg}"
        stats = result.get("stats") or result
        return (
            f"Agent Identity: {stats.get('agent_author')}\n"
            f"  total_uploads:        {stats.get('total_uploads')}\n"
            f"  total_claimed:        {stats.get('total_claimed')}\n"
            f"  total_expired:        {stats.get('total_expired')}\n"
            f"  claim_success_rate:   {stats.get('claim_success_rate')}\n"
            f"  contact_email_verified: {stats.get('contact_email_verified')}\n"
            f"  claimed:              {stats.get('claimed')}\n"
            f"  first_upload_at:      {stats.get('first_upload_at', '—')}"
        )
  • The tool is registered via @mcp.tool() and @_log_tool decorators on line 758-759. The @mcp.tool() registers this function as an MCP tool named 'get_agent_identity_stats' with the FastMCP instance.
    @mcp.tool()
    @_log_tool
  • The _get() helper function is used by the handler to make the actual HTTP GET request to the backend API endpoint. It constructs the URL, handles HTTP errors, and returns parsed JSON.
    def _get(path: str, params: dict = None) -> dict:
        url = SKILL_STORE_URL + path
        if params:
            url += "?" + urllib.parse.urlencode({k: v for k, v in params.items() if v is not None})
        try:
            with urllib.request.urlopen(url, timeout=10) as resp:
                return json.loads(resp.read().decode())
        except urllib.error.HTTPError as e:
            return {"status": "error", "message": f"HTTP {e.code}: {e.reason}"}
        except Exception as e:
            return {"status": "error", "message": str(e)}
  • Schema/docstring defining the tool's input (agent_name: str) and output (formatted string with total_uploads, total_claimed, total_expired, claim_success_rate, contact_email_verified summary).
    """
    Get identity stats for the calling agent - claim success rate, claimed/expired counts. / 에이전트 단위 claim 통계.
    특정 agent_author 가 업로드한 Draft 들의 claim_success_rate / expire_rate 를 공개 조회.
    
    Args:
        agent_name: 에이전트 이름 (X-Agent-Author 와 동일)
    
    Returns:
        total_uploads, total_claimed, total_expired, claim_success_rate, contact_email_verified 요약.
    """
Behavior2/5

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

Annotations are absent, so the description carries full burden. It fails to disclose whether the tool is read-only, requires authentication, or has rate limits. It mentions the returned statistics but does not state side effects or behavior beyond data retrieval. For a stats-gathering tool, this is minimal.

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?

The description is bilingual but not overly long, with clear 'Args' and 'Returns' sections. It avoids redundancy, though the initial line and Korean text could be merged. Overall, it is well-structured and each part adds value.

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?

Given the presence of an output schema, the description does not need to detail return values, but it lists them anyway, which is helpful. However, it lacks usage context and behavioral transparency. For a single-parameter tool with no annotations, it covers basic functionality but leaves gaps in when and how to use it.

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 description adds meaning to the single required parameter 'agent_name' by stating it must match the X-Agent-Author header. With 0% schema description coverage, this helps, but it does not provide format, validation rules, or examples. The schema itself only specifies type string, so the description provides some but not full compensation.

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 the tool returns identity statistics for an agent, specifically claim success rate and counts. It distinguishes from siblings like get_agent_author_stats by focusing on claims and using the Korean text to clarify it queries drafts uploaded by the agent author. The verb 'Get' and resource 'identity stats' are explicit.

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 on when to use this tool versus alternatives like get_agent_author_stats or check_draft_status. The description does not mention prerequisites, context, or exclusions. The Korean phrase '공개 조회' (public inquiry) hints at accessibility but does not provide concrete usage direction.

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/garasegae/aiskillstore'

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