Skip to main content
Glama

agentfolio_endorsements

Retrieve endorsements for any agent: see who endorsed them and which skills were endorsed.

Instructions

Get endorsements for an agent — who endorsed them and what skills they endorsed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID to get endorsements for

Implementation Reference

  • Handler for agentfolio_endorsements: tries two API endpoints (/profile/{agent_id}/endorsements and /endorsements/{agent_id}) using apiSoft fallback, returns endorsements data or an error if both endpoints are unavailable.
    case "agentfolio_endorsements": {
      // Try both possible endorsement endpoints
      const endorsements = await apiSoft(
        `/profile/${args.agent_id}/endorsements`,
        await apiSoft(`/endorsements/${args.agent_id}`, null)
      );
      if (!endorsements) {
        return JSON.stringify({
          agent_id: args.agent_id,
          error: "Endorsements endpoint is currently unavailable",
          note: "The AgentFolio endorsements API may be undergoing maintenance.",
        }, null, 2);
      }
      return JSON.stringify(endorsements, null, 2);
    }
  • Input schema for agentfolio_endorsements tool: requires agent_id (string) with no optional parameters.
    {
      name: "agentfolio_endorsements",
      description:
        "Get endorsements for an agent — who endorsed them and what skills they endorsed.",
      inputSchema: {
        type: "object",
        properties: {
          agent_id: {
            type: "string",
            description: "Agent ID to get endorsements for",
          },
        },
        required: ["agent_id"],
      },
    },
  • src/index.js:437-440 (registration)
    The TOOLS array (which includes agentfolio_endorsements) is registered via the ListToolsRequestSchema handler, making the tool available to MCP clients.
    // List tools
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • src/index.js:442-456 (registration)
    The CallToolRequestSchema handler dispatches incoming tool calls to handleTool(), routing to the agentfolio_endorsements case in the switch statement.
    // Call tool
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      try {
        const result = await handleTool(name, args || {});
        return {
          content: [{ type: "text", text: result }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: ${err.message}` }],
          isError: true,
        };
      }
    });
  • The apiSoft helper used by the endorsements handler to gracefully fall back between API endpoints without throwing errors.
    // Soft API call — returns fallback on error instead of throwing
    async function apiSoft(path, fallback = null) {
      try {
        return await api(path);
      } catch {
        return fallback;
      }
    }
Behavior3/5

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

Annotations are absent, so the description carries full burden. It correctly implies a read operation but does not disclose any limitations, error cases, or response behavior. Minimal transparency is provided.

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?

One sentence, clear and direct, with no unnecessary words. Every part earns its place.

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?

Given the simplicity (single parameter, no output schema, no annotations), the description is nearly complete. It could mention what happens on invalid or missing endorsements, but overall it sufficiently informs the agent.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter description. No format or validation details are given for agent_id.

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?

Description clearly states the verb 'Get' and the resource 'endorsements for an agent', and specifies the returned information (who endorsed and what skills). It distinguishes this tool from sibling tools like agentfolio_list_agents or agentfolio_lookup by focusing specifically on endorsements.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or context. The description lacks explicit when-to-use or when-not-to-use information.

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