Skip to main content
Glama

fund_campaign

Build an unsigned Solana transaction to fund a campaign on Clawsfund, using campaign ID, amount, and backer public key.

Instructions

Build an unsigned Solana transaction to fund a Clawsfund campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
campaignIdYes
backerPublicKeyYes
Behavior3/5

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

The description discloses the key behavioral trait that the transaction is unsigned, indicating no finalization. However, since no annotations are provided, the description carries full burden and omits details like side effects, authorization needs, or rate limits.

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, focused sentence with no redundant information, but could benefit from additional structure to list key aspects.

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?

The description fails to mention the return value (expected to be an unsigned transaction), and does not explain parameters. Given three required parameters and no output schema, the description is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not elaborate on the meaning or constraints of any parameter (campaignId, amount, backerPublicKey). The agent must rely only on parameter names, which is insufficient.

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?

The description clearly states the verb ('build'), resource ('unsigned Solana transaction'), and the domain ('fund a Clawsfund campaign'). It distinguishes from sibling tools which focus on querying or listing campaigns, not funding.

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, no prerequisites or when-not-to-use. The description only implies usage for funding but lacks explicit 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/tashfeenahmed/clawsfund-mcp'

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