Skip to main content
Glama

Binance Smart Chain: isFourMemeToken

isFourMemeToken
Read-onlyIdempotent

Identify if a token address corresponds to a FourMeme token on the BSC network.

Instructions

Check if a token is a FourMeme token on BSC

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenAddressNoThe token address to check
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the tool's behavioral traits are clear. The description adds no extra context beyond what the annotations provide, but it does not contradict them.

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 is a single sentence that front-loads the purpose with no wasted words. It is efficient and immediately understandable.

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

Completeness4/5

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

Given the tool's simplicity (one parameter, no output schema) and the rich annotations, the description is nearly complete. It could optionally mention the output type (boolean), but the tool name implies a boolean check, so it is sufficient.

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

Parameters3/5

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

The input schema covers 100% of parameters with a description ('The token address to check'). The description does not add additional meaning such as expected format or validation rules, so it meets the baseline but does not exceed it.

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 explicitly states the action ('Check'), the resource ('token is a FourMeme token'), and the chain ('on BSC'). It clearly distinguishes from sibling tools like bscfindMemeCoinsViaFourMeme by focusing on checking a specific token rather than finding new ones.

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 does not provide any guidance on when to use this tool over alternatives or any prerequisites. It is minimal and leaves the agent to infer usage context, which is slightly below the standard for explicit guidance.

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