Skip to main content
Glama
Sign In
bca-mcp

bca-mcp

by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_marketing_templates

Lists marketing campaign templates including TGE checklist, airdrop ops, NFT mint script, influencer brief, and press kit. Starter tier.

Instructions

Campaign templates: TGE checklist, airdrop ops, NFT mint script, influencer brief, press kit. Starter tier.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_marketing_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only lists contents and mentions 'Starter tier' but fails to mention any auth, rate limits, pagination, or data freshness. The behavioral impact is under-disclosed.

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 concise sentence that front-loads the core purpose. Every part adds information without redundancy, making it efficient.

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?

Given the tool's simplicity (no params, no output schema, no annotations), the description adequately covers what templates are listed but does not mention output format, limitations, or whether results are paginated. The 'Starter tier' hint is useful but incomplete.

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

Parameters4/5

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

The input schema has zero parameters, so no parameter documentation is needed. The description adds value by listing the types of templates included, which is relevant context beyond the schema.

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 indicates the resource (campaign templates) and provides specific examples (TGE checklist, airdrop ops, etc.), distinguishing it from sibling tools like get_marketing_template and list_smart_contract_templates. The verb 'list' is implicit from the tool name, and the description adds context.

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 through 'Starter tier' but does not explicitly state when to use this tool versus alternatives or when not to use it. No direct guidance on context or exclusion is provided.

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