Skip to main content
Glama
Sign In
bca-mcp

bca-mcp

by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_rwa_tokens

Retrieve real-world asset tokenization data with a configurable limit. Track tokenized assets from the starter tier.

Instructions

Real-world asset tokenization tracker. 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": "get_rwa_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description must fully communicate behavioral aspects. It only says 'tracker', implying read-only, but lacks details on output format, pagination, rate limits, or any side effects. This is insufficient for an agent to understand behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), which is concise but at the cost of essential information. It could be restructured to include more detail without being verbose, but as is, it sacrifices clarity for brevity.

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?

Given the tool has only one optional parameter and no output schema, the description still fails to explain what the tool returns, how the limit works, or any authentication requirements. It is not complete enough for an agent to use effectively.

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?

The schema has a single 'limit' parameter with 0% description coverage, and the tool description does not address it. The agent receives no help on what the parameter does, how it affects results, or its acceptable values beyond basic constraints in 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 states 'Real-world asset tokenization tracker', which clearly identifies the tool's focus on RWA tokenization, distinguishing it from many sibling tools that cover other crypto topics. However, the phrase 'Starter tier' is ambiguous and does not add clarity.

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 is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage without support.

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