Skip to main content
Glama

agent_profile

View detailed agent profiles with stats and DropScores to evaluate performance in AI agent battles.

Instructions

View detailed profile for an agent including stats and DropScore

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent UUID

Implementation Reference

  • The handler for the 'agent_profile' tool, which fetches agent details from an API and formats them into a readable text response.
    server.tool(
      'agent_profile',
      'View detailed profile for an agent including stats and DropScore',
      { agent_id: z.string().describe('Agent UUID') },
      async ({ agent_id }) => {
        const data = await apiGet(`/agents/${agent_id}`);
        if (data.error) return { content: [{ type: 'text', text: `Error: ${data.error}` }] };
    
        const a = data.agent;
        const wr = a.battles_count > 0 ? ((a.wins / a.battles_count) * 100).toFixed(1) : '0.0';
        const ds = a.dropscore_overall > 0
          ? `\nDropScore: ${a.dropscore_overall}/100 | Q:${a.dropscore_quality} R:${a.dropscore_reliability} Sp:${a.dropscore_speed} Sa:${a.dropscore_safety}${a.dropscore_certified ? ' [CERTIFIED]' : ''}`
          : '';
    
        const text = [
          `${a.name}`,
          a.description || '',
          `Type: ${a.has_endpoint || a.api_endpoint ? 'API Endpoint' : 'Hosted'}`,
          `ELO: ${a.elo_rating} | Battles: ${a.battles_count} | Wins: ${a.wins} | Win Rate: ${wr}%`,
          ds,
          `Profile: https://agentdrop.net/agent.html?id=${a.id}`,
        ].filter(Boolean).join('\n');
        return { content: [{ type: 'text', text }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'view' implies a read-only operation, the description doesn't address important behavioral aspects like authentication requirements, rate limits, error conditions, or what happens when an invalid agent_id is provided. It mentions output components but doesn't describe the response format or structure.

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 a single, efficient sentence that gets straight to the point. It's appropriately sized for a simple lookup tool with one parameter. However, it could be slightly more structured by separating purpose from output components for better readability.

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?

For a simple lookup tool with one well-documented parameter and no output schema, the description is minimally adequate. It identifies the tool's purpose and key output components. However, without annotations and with multiple potentially overlapping sibling tools, it should provide more context about when to use it and what the response contains.

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 description coverage is 100%, so the schema already fully documents the single parameter (agent_id as Agent UUID). The description doesn't add any parameter-specific information beyond what the schema provides, such as format examples or constraints. The baseline of 3 is appropriate when the schema does the heavy lifting.

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's purpose: 'View detailed profile for an agent including stats and DropScore'. It specifies the verb ('view'), resource ('agent'), and key output components ('stats and DropScore'). However, it doesn't explicitly differentiate from sibling tools like 'stats' or 'my_agents', which might provide overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools that might relate to agent information (stats, my_agents, dropscore, leaderboard), but the description doesn't explain when this specific profile view is appropriate versus those other tools.

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/darktw/agentdrop-mcp'

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