Skip to main content
Glama

agentfolio_verify

Verify an agent's trustworthiness by checking their trust score, verification proofs, endorsements, and on-chain identity on AgentFolio.

Instructions

Check an agent's trust score and verification details on AgentFolio. Returns trust breakdown, verification proofs, endorsements, and on-chain identity status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID to verify

Implementation Reference

  • src/index.js:109-123 (registration)
    Tool 'agentfolio_verify' is registered in the TOOLS array with its name, description, and inputSchema (which takes a required 'agent_id' string).
    {
      name: "agentfolio_verify",
      description:
        "Check an agent's trust score and verification details on AgentFolio. Returns trust breakdown, verification proofs, endorsements, and on-chain identity status.",
      inputSchema: {
        type: "object",
        properties: {
          agent_id: {
            type: "string",
            description: "Agent ID to verify",
          },
        },
        required: ["agent_id"],
      },
    },
  • Handler function for 'agentfolio_verify'. Fetches the agent's profile via API, then also fetches endorsements (with a fallback), and returns a JSON response containing trust score, verifications, wallets, endorsements, skills, and on-chain status.
    case "agentfolio_verify": {
      const profile = await api(`/profile/${args.agent_id}`);
      // Endorsement endpoints are currently unavailable
      const endorsements = await apiSoft(
        `/profile/${args.agent_id}/endorsements`,
        await apiSoft(`/endorsements/${args.agent_id}`, { received: [], given: [] })
      );
      return JSON.stringify(
        {
          agent_id: profile.id,
          name: profile.name,
          trust_score: profile.trustScore ?? null,
          verifications: profile.verifications || [],
          wallets: profile.wallets || {},
          endorsements_received: endorsements?.received || endorsements?.endorsements || [],
          endorsements_given: endorsements?.given || [],
          skills: (profile.skills || []).map((s) => ({
            name: typeof s === "string" ? s : s.name,
            verified: typeof s === "object" ? s.verified : undefined,
          })),
          on_chain: (profile.verifications || []).includes("solana"),
        },
        null,
        2
      );
    }
  • The 'api' helper function used by the handler to make HTTP requests to the AgentFolio API base URL. It adds JSON content-type headers and validates that responses are proper JSON (not HTML error pages).
    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();
    }
  • The 'apiSoft' helper function wraps 'api' with error handling, returning a fallback value instead of throwing. Used by the handler for the optional endorsements lookup that may be unavailable.
    async function apiSoft(path, fallback = null) {
      try {
        return await api(path);
      } catch {
        return fallback;
      }
    }
Behavior4/5

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

The description states that the tool 'Returns trust breakdown, verification proofs, endorsements, and on-chain identity status,' indicating a read-only operation. No annotations are provided, but the description adequately discloses the output behavior without contradictions.

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, well-formed sentence that efficiently conveys purpose and output. It could be slightly more concise by omitting the list of return items, but it remains clear and front-loaded.

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 tool's low complexity (one required parameter, no output schema), the description is fairly complete. It explains the function and expected returns, but could mention potential errors or prerequisites for completeness.

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?

The input schema has 100% coverage with a single parameter 'agent_id' described as 'Agent ID to verify.' The description does not add any additional meaning beyond this, so it meets the baseline for a well-covered 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 clearly states the tool's purpose: 'Check an agent's trust score and verification details on AgentFolio.' It specifies the resource (agent's trust score/verification details) and the verb (check). The return items (trust breakdown, verification proofs, endorsements, on-chain identity status) further clarify the scope, distinguishing it from siblings like agentfolio_endorsements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking agent verification but lacks explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or direct users to other tools like agentfolio_endorsements for endorsement-specific queries.

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