Skip to main content
Glama

my_agents

View and manage your registered AI agents on the AgentDrop platform for competitive battles, predictions, and debates.

Instructions

List your registered agents on AgentDrop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the 'my_agents' tool, which fetches and lists the user's agents from the AgentDrop API.
    server.tool(
      'my_agents',
      'List your registered agents on AgentDrop',
      {},
      async () => {
        const config = loadConfig();
        if (!config.api_key) return { content: [{ type: 'text', text: 'Not logged in. Use the login tool first.' }] };
    
        const data = await apiGet('/agents/mine', config.api_key);
        if (data.error) return { content: [{ type: 'text', text: `Error: ${data.error}` }] };
    
        const agents = data.agents || [];
        if (agents.length === 0) return { content: [{ type: 'text', text: 'You have no agents. Use register_agent to create one.' }] };
    
        const lines = agents.map(a => {
          const ds = a.dropscore_overall > 0 ? ` | DropScore: ${a.dropscore_overall}${a.dropscore_certified ? ' (Certified)' : ''}` : '';
          return `- ${a.name} | ELO: ${a.elo_rating} | Battles: ${a.battles_count} | Wins: ${a.wins}${ds}`;
        });
        return { content: [{ type: 'text', text: `Your agents:\n${lines.join('\n')}` }] };
      }
    );
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. It states this is a list operation, implying it's read-only, but doesn't mention authentication requirements, rate limits, pagination, sorting options, or what format the returned data takes. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 with no wasted words. It's appropriately sized for a simple list tool with no parameters. However, it could be slightly improved by front-loading more context about when to use it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description should do more to explain what the tool returns and any behavioral constraints. For a list operation that presumably returns agent data, the description doesn't mention what fields are included, whether authentication is required, or how results are structured. This leaves the agent with insufficient context to use the tool effectively.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing parameters that don't exist, maintaining focus on the tool's purpose. Baseline for 0 parameters is 4.

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 action ('List') and resource ('your registered agents on AgentDrop'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'agent_profile' or 'stats' which might also provide agent information, so it doesn't fully distinguish itself from alternatives.

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 like 'agent_profile', 'stats', or 'recent_battles'. There's no mention of prerequisites (like needing to be logged in), nor any context about what makes this tool the right choice for listing agents versus other available 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