Skip to main content
Glama

Binance Smart Chain: bscfindMemeCoinsViaFourMeme

bscfindMemeCoinsViaFourMeme
Read-onlyIdempotent

Find meme coins on Binance Smart Chain by filtering via FourMeme. Sort by hotness, progress, or time; filter by labels like AI, Meme, or DeFi.

Instructions

Find meme coins on BSC via FourMeme. Market cap is in BNB, price in USD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderByNoHot
tokenNameNo
listedPancakeNo
pageIndexNo
pageSizeNo
symbolNo
labelsNo
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering basic safety. The description adds value by noting that market cap is in BNB and price in USD, which is behavioral output context. However, no other behavioral traits (pagination, rate limits, default sorting) are disclosed.

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?

The description consists of two concise sentences that front-load the core purpose. Every word is relevant, and there is no superfluous information.

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 7 parameters with no schema descriptions and a large sibling set, the description is too sparse. It omits parameter semantics, usage guidelines, and behavioral details beyond output units, making it incomplete for effective agent use.

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 description coverage is 0%, meaning the input schema has no property descriptions. The tool description does not explain any of the 7 parameters (orderBy, tokenName, listedPancake, pageIndex, pageSize, symbol, labels), leaving the agent to rely on parameter names alone. This is a significant gap.

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 clearly states the tool finds meme coins on BSC via FourMeme, specifying the action (find), subject (meme coins on BSC), and source (FourMeme). It also provides additional info about output units (market cap in BNB, price in USD), which distinguishes it from similar tools like hederaFindMemeCoins.

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?

The description lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it. Given the large number of sibling tools, explicit usage context is missing.

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/EmblemCompany/Agent-skills'

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