Skip to main content
Glama

Get asset

get_asset
Read-only

Use when investigating what people said about a particular asset over a chosen period. For many selected coins prefer get_assets when advertised. Through OpenAI programmatic tools await at most two independent calls together; retain complete results and emit requested summaries/decisive evidence rather than printing all raw payloads. Returns its identity, posts, whole-window activity counts and engagement_summary together. The first-page summary measures all matching posts and returns exact totals, leading author rankings by summed counters and highest single-post views; use it instead of scanning every post for a numeric ranking. Choose projection=market for claims: it returns full retained text plus publication-time estimates and separate ingestion captures in this same request. Reuse the returned series_id with get_market_history for subsequent prices. This result is not a current quote or candle curve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExplore retains up to 500 matches. Exhaustive retains every match for an accepted scope up to 5000; larger scopes fail explicitly so you can partition dates. Continuations last 30 minutes.explore
textNo
limitNoPage size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size.
orderNotime_balanced interleaves seven equal parts of the requested period before the retention limit; useful for broad discussion research, not statistical sampling.newest
cursorNoPass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query.
detailNoCompact reading evidence by default. Choose market to include full stored capture and publication-price provenance for every post.compact
date_toYesExclusive UTC end; required.
asset_idYes
asset_idsNoCanonical asset IDs from resolve_assets, not tickers or provider IDs.
chain_idsNoCoin chain IDs, e.g. solana, ethereum, base, robinhood. Includes confirmed stored V1, native and multichain associations; candidates, expired and unknown associations are excluded. Posts qualify through their attached coins.
date_fromYesInclusive UTC start; required. Maximum window 366 days.
has_mediaNo
asset_typeNoKnown asset relationship. With chain_ids, type must match on one of those chains; native and token relationships may coexist across chains. Unknown has no classified relationship.
author_idsNoCanonical author IDs from search_authors, not X handles or user IDs.
multichainNoTrue selects assets with at least two known chains. False means fewer than two KNOWN chains, not proven single-chain.
post_typesNo
projectionNoindex omits text; preview returns short text; reading returns full retained text and relations without prices; market includes price evidence.
evidence_classNoFilter standalone collected evidence versus retained embedded quote evidence; omitted includes both.
exclude_post_typesNoExclude selected types; excluding original also excludes historical unknown labels, while excluding repost keeps ordinary unknown labels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Page size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size."
  2. Changed1 schema field changed
    • addedInput schema / properties / text / properties / full_text_query / description
      Added value: +"Space-separated AND, spaced OR, quoted phrases and minus exclusions. No stemming: agent and agents differ. Unquoted parentheses unsupported; repeat common terms, e.g. AI agent OR AI agents."
  3. Changed2 schema fields changed
    • addedInput schema / properties / asset_ids / description
      Added value: +"Canonical asset IDs from resolve_assets, not tickers or provider IDs."
    • addedInput schema / properties / author_ids / description
      Added value: +"Canonical author IDs from search_authors, not X handles or user IDs."
  4. Changed1 schema field changed
    • changedInput schema / properties / exclude_post_types / description
      Previous value: -"Exclude only known types; excluding repost keeps unknown types."New value: +"Exclude selected types; excluding original also excludes historical unknown labels, while excluding repost keeps ordinary unknown labels."
  5. Changed1 schema field changed
    • addedInput schema / properties / cursor / description
      Added value: +"Pass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query."
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description focuses on behavior: the first-page summary measures all matching posts and returns exact totals, top authors and highest single-post views, and it warns the result is not a live quote. It stops short of detailing pagination/cursor lifecycle or error behavior beyond what the schema states.

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?

Front-loaded with the triggering condition and dense with useful information, but the middle section drifts into generic agent-operating advice ('await at most two independent calls together; retain complete results and emit requested summaries') that is not tool-specific and crowds the tool-relevant routing sentences. Several sentences are long and multi-clause.

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?

With 19 parameters and no output schema, the description compensates well by describing the returned fields and the first-page summary semantics. It remains incomplete on how the many filter parameters interact (chain_ids + asset_type, exclude_post_types) and on pagination behavior for large result sets.

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

Parameters4/5

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

Schema coverage is 79% (high), so baseline is 3, but the description adds real meaning for projection=market ('full retained text plus publication-time estimates and separate ingestion captures') that the schema's one-line enum gloss doesn't convey. It does not clarify the overlap between the schema's detail=market and the description's projection=market, which risks confusion.

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 opening sentence states a specific verb and resource ('investigating what people said about a particular asset over a chosen period') and enumerates the payload shape (identity, posts, whole-window activity counts, engagement_summary). It explicitly distinguishes itself from siblings get_assets and get_market_history, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit branching: prefer get_assets for many coins, use the first-page summary instead of scanning every post for rankings, choose projection=market for claims, and reuse series_id with get_market_history. It also explains what projection=market returns versus what this result is not ('not a current quote or candle curve').

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