Skip to main content
Glama

Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking

by com.onvexia
OverviewDiscussionsAdmin

Fundamentals · Full brief

get_asset_fundamentals
Read-onlyIdempotent

Get the full fundamental brief for an asset: market snapshot, supply and valuation, project, TVL, revenue, treasury, security, governance, unlock schedule, derivatives positioning, competitive rank, valuation ratios and a graded scorecard — in one call.

    READ THE SECTION STATES, NOT ONLY THE VALUES. Each section is
    `measured`, `not_held` or `failed`, and sections the asset class cannot
    have are returned separately in `not_applicable`. "This chain has no
    DAO treasury" and "we could not read it" are different facts and this
    response keeps them apart.

    Revenue is split: `S06` is the entity's own fees, `S06b` is the total
    earned by protocols deployed on a chain. The two can differ by two
    orders of magnitude and only the first accrues to the token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare the call read-only and idempotent, and the description adds valuable interpretation semantics beyond that: section states measured/not_held/failed vs not_applicable, the distinction between 'no treasury' and 'could not read it', and the S06 vs S06b revenue split. This is exactly the kind of behavioral context that prevents misinterpretation.

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

Conciseness4/5

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

The description is longer than average but front-loads the main purpose and then provides genuinely important caveats. The all-caps warning and revenue split explanation earn their place, though some phrasing could be tightened.

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?

There is no output schema, so the description carries the burden of explaining return semantics; it does cover the most important ones: section states, not_applicable handling, and revenue split. It does not detail the full response shape or grading scale, but the listed components and caveats are sufficient for correct tool selection and interpretation.

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?

Schema coverage is 0% and the description does not explain what values 'symbol' accepts, whether it is a ticker, asset ID, or address, or provide examples. The only hint is the phrase 'for an asset', which adds minimal meaning beyond the property title. With no schema description, the tool description should compensate but does not.

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?

Description states a specific verb and resource: 'Get the full fundamental brief for an asset' and enumerates its many components, making it distinct from sibling tools like get_asset_scores or get_asset_technicals. The scope is clear and immediately actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when a comprehensive fundamental overview is needed ('in one call') and provides guidance on how to interpret the returned sections. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to route correctly.

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

All Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources