Skip to main content
Glama
ocbenji

@bitcoinbenji/mcp

ai_sentiment

Analyze sentiment of text with a confidence score. Pay 10 sats per call via Lightning.

Instructions

Sentiment analysis with confidence score. [10 sats per call]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
preimageNo(L402 mode) Preimage from paid Lightning invoice — only needed if no API key is set
macaroonNo(L402 mode) Macaroon from the previous 402 challenge
Behavior2/5

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

Lacks disclosure of behavioral traits such as authentication requirements (L402 explained in schema but not description), error handling, or what happens with empty inputs; cost mentioned but insufficient for full transparency.

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?

Very short and front-loaded with purpose and cost, but omits critical details like authentication and output format, making it under-specified rather than concise.

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?

Incomplete for a tool with no output schema and moderate schema coverage; missing context about input constraints, output format, and auth flow.

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?

Description adds no extra meaning to parameters beyond schema; the required 'text' parameter has no description in either, and L402 fields are only partially explained in schema.

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?

Clearly states the tool performs 'sentiment analysis with a confidence score', which is specific and distinct from siblings like ai_classify or ai_summarize.

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 on when to use this tool versus other AI tools like ai_classify for sentiment tasks; no mention of prerequisites or exclusions.

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/ocbenji/bitcoinbenji-mcp'

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