Skip to main content
Glama

agentfolio_marketplace_stats

Retrieve AgentFolio marketplace statistics including total agents, skills, verified agents, and on-chain registrations.

Instructions

Get AgentFolio marketplace statistics — total agents, skills, verified count, and on-chain registrations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool schema definition for agentfolio_marketplace_stats — declares the tool's name, description, and empty input schema.
    {
      name: "agentfolio_marketplace_stats",
      description:
        "Get AgentFolio marketplace statistics — total agents, skills, verified count, and on-chain registrations.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler implementation for agentfolio_marketplace_stats — fetches profiles and jobs data via apiSoft, computes total agents, total jobs, and open jobs, then returns JSON.
    case "agentfolio_marketplace_stats": {
      // /marketplace/stats endpoint is currently unavailable — compute from available data
      const [profilesData, jobsData] = await Promise.all([
        apiSoft("/profiles", { profiles: [], total: 0 }),
        apiSoft("/marketplace/jobs", { jobs: [], total: 0 }),
      ]);
      return JSON.stringify(
        {
          totalAgents: profilesData.total || (profilesData.profiles || []).length,
          totalJobs: jobsData.total || (jobsData.jobs || []).length,
          openJobs: (jobsData.jobs || []).filter((j) => j.status === "open").length,
          note: "Stats computed from available API endpoints. Some metrics may be approximate.",
        },
        null,
        2
      );
    }
  • src/index.js:438-440 (registration)
    Registration via ListToolsRequestSchema — the TOOLS array (which includes agentfolio_marketplace_stats) is returned to the MCP client on a list-tools request.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • Helper function apiSoft — wraps api() to return a fallback on error instead of throwing, used by the marketplace_stats handler.
    // Soft API call — returns fallback on error instead of throwing
    async function apiSoft(path, fallback = null) {
      try {
        return await api(path);
      } catch {
        return fallback;
      }
    }
Behavior2/5

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

No annotations provided, so the description must carry the full burden. It states 'Get' implying a read operation, but does not disclose potential rate limits, authentication needs, or other behavioral traits. Lacks depth.

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?

A single, well-structured sentence front-loads the purpose and lists deliverables without superfluous words.

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?

For a simple stats tool with no parameters or output schema, the description sufficiently conveys what the agent gets. Could mention return format or error cases, but overall adequate.

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?

There are zero parameters, so schema coverage is 100%. The description adds value by enumerating the returned data categories, going beyond the empty schema.

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 specifies 'Get AgentFolio marketplace statistics' and lists the exact data points (total agents, skills, verified count, on-chain registrations), making the purpose clear and distinct from sibling tools like agentfolio_list_agents.

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 vs alternatives, nor any exclusions or prerequisites. The description only states what it does without context for selection.

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