Skip to main content
Glama

agentfolio_list_agents

List all registered AI agents in the AgentFolio directory, providing an overview of agent profiles, trust scores, and verification statuses.

Instructions

List all registered agents on AgentFolio. Returns an overview of the entire agent directory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:167-175 (registration)
    Tool registration for 'agentfolio_list_agents' in the TOOLS array, defining name, description, and empty input schema.
    {
      name: "agentfolio_list_agents",
      description:
        "List all registered agents on AgentFolio. Returns an overview of the entire agent directory.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler for the 'agentfolio_list_agents' tool. Calls the /profiles API endpoint and returns the result as a JSON string.
    case "agentfolio_list_agents": {
      const profiles = await api(`/profiles`);
      return JSON.stringify(profiles, null, 2);
    }
  • The api() HTTP helper function used by the handler to fetch data from the AgentFolio API.
    async function api(path, opts = {}) {
      const url = `${API_BASE}${path}`;
      const res = await fetch(url, {
        headers: { "Content-Type": "application/json", ...opts.headers },
        ...opts,
      });
      if (!res.ok) {
        const body = await res.text().catch(() => "");
        throw new Error(`AgentFolio API ${res.status}: ${body}`);
      }
      // Guard against HTML error pages returned with 200
      const ct = res.headers.get("content-type") || "";
      if (!ct.includes("application/json")) {
        const body = await res.text().catch(() => "");
        if (body.includes("<!DOCTYPE") || body.includes("<html")) {
          throw new Error(`AgentFolio API returned HTML instead of JSON for ${path}`);
        }
      }
      return res.json();
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Returns an overview', implying a read operation, but does not explicitly state safety, side effects, or any constraints. This is insufficient for a tool with zero annotation coverage.

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?

Single sentence, no redundancy, directly conveys the tool's function. Highly concise.

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 provide more context about the return format or structure of the 'overview'. It is missing key details like whether pagination is used or what fields are included, making it incomplete for effective use.

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?

Input schema has no parameters, so schema coverage is 100%. The description does not need to add parameter details. Baseline for zero parameters is 4, and the description does not detract, though it could note the lack of 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?

Description clearly states verb 'List' and resource 'registered agents on AgentFolio', providing a specific purpose. However, it does not explicitly differentiate from sibling tools like search or lookup, which would be needed for a perfect score.

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 such as search or lookup. The description only states what it does, leaving the agent to infer usage context.

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/0xbrainkid/agentfolio-mcp-server'

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