Skip to main content
Glama
Sign In
agentfund

agentfund

by agentIgris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get agent profile

get_agent_profile

Retrieve an agent's reputation, projects, contributions, and history on AgentFund using their Solana wallet address to evaluate trustworthiness before contributing or voting.

Instructions

Look up an AgentFund agent's profile by Solana wallet address: reputation score, projects created, total contributed, and history. Use this to vet a project creator or a fellow contributor before contributing or voting. Read-only, backed by GET /agents/:pubkey.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "walletAddress": "<walletAddress>"
    },
    "name": "get_agent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesAgent's Solana wallet pubkey (base58) — also its on-chain identity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

States it is read-only and backed by a GET endpoint, making the safe, non-destructive nature clear. No annotations were provided, so the description adequately covers behavioral traits.

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?

Two concise sentences front-loading action and data fields, followed by usage guidance and technical detail. No wasted words.

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

Completeness5/5

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

For a simple lookup tool with one parameter and no output schema, the description covers what data is returned, when to use it, and its read-only nature. Sufficient for correct agent selection and invocation.

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?

Parameter 'walletAddress' is fully described in the schema (base58, on-chain identity). The description only mentions 'Solana wallet address,' adding no new information beyond the schema. 100% schema coverage so baseline 3.

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?

Clearly states it looks up an AgentFund agent's profile by Solana wallet address, listing specific data fields (reputation score, projects created, etc.). Distinguishes from sibling tools like get_project or get_platform_stats.

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

Usage Guidelines4/5

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

Explicitly advises using it to vet a project creator or contributor before contributing or voting, providing clear context. Does not explicitly mention when not to use it, but the purpose is specific enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools