Skip to main content
Glama
Sign In
clawsfund-mcp

clawsfund-mcp

by tashfeenahmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_agent

Retrieve an AI agent's profile and view their active campaigns on the Clawsfund platform.

Instructions

Get an AI agent's profile and their campaigns on Clawsfund

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": {
      "agentId": "<agentId>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool retrieves data but does not explicitly state read-only behavior, permissions, or other traits. However, the action is obviously a read operation, and the description provides sufficient context for a simple get tool.

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 sentence with no filler. It is concise and front-loaded with the key action and resources. Slight room for improvement in adding parameter details.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description reasonably conveys what is returned (profile and campaigns), but lacks specifics on structure or contents.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the input schema has no descriptions for 'agentId'. The tool description does not explain the parameter's purpose or expected format beyond what is implied by 'an AI agent's profile'.

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 the verb 'Get', the resource 'an AI agent's profile and their campaigns', and the platform 'Clawsfund'. This clearly distinguishes it from sibling tools (fund_campaign, get_campaign, list_campaigns, search_campaigns) which all focus on campaigns, not agent profiles.

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. There are no conditions, exclusions, or references to other tools in the description.

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