Skip to main content
Glama

bioaura_dataset

Full BioAura dataset (JSON): 7 chakras with all practices, 52 stones, 98 check-up statements and scoring keys. For apps and agents (licence included). Price: $1.00 USDC per call (x402).

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": "bioaura_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the two most consequential traits: this is a paid call ($1.00 USDC via x402) and the licence is included. It stops short of explaining how payment is negotiated, what happens on an unpaid call, or how large the JSON payload is, which are meaningful gaps for a paid tool.

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?

Two sentences, no filler. The payload contents and format come first, followed by audience, licence, and price — the ordering an agent needs to decide whether to spend a paid call.

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?

For a single-call bulk-data tool with one optional parameter and no output schema, the description covers what is returned, in what format, for whom, and at what cost. What remains thin is the payment flow and response size, which matter given the per-call charge, but nothing essential to selecting the tool is missing.

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?

There is one optional parameter (lang, enum it/en) and schema description coverage is 100%, so the schema already documents it, including the default. The description adds nothing about what language affects (it mentions "core texts" nowhere), so it neither compensates nor detracts. Baseline 3 applies when the schema does the work.

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 names a specific resource (the full BioAura dataset) and enumerates its contents: 7 chakras with practices, 52 stones, 98 check-up statements, plus scoring keys. That is far more concrete than a tautology. It falls short of a 5 because it does not contrast itself with near-name siblings such as library_full_dataset or library_collection_dataset, leaving the agent to infer the boundary from names alone.

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?

"For apps and agents" hints at the intended consumer (bulk-data clients rather than single-record lookups), which is implied usage rather than explicit guidance. There is no statement of when NOT to use it or which sibling to prefer for narrower queries, even though several dataset/list tools sit alongside it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources