Analyzera

Compare instruments

describe_assets

Read-onlyIdempotent

Headline figures for up to 500 instruments in one call, one line each.

The comparison form of ``describe_asset``, for a screen's companies or any list
of ids: 1Y return, volatility and maximum drawdown, 3Y annualised return, P/E,
dividend yield and market cap, in the client's currency. ``fields`` adds groups:
'classification' (ISIN, GICS industry, size segment, themes), 'valuation' (P/B,
P/S, EV/market cap), 'quality' (ROE, ROA), 'growth' (the screener's growth score
and its parts), 'factors' (``describe_asset``'s tilts) and 'esg' (score and
exclusion). Ask only for the groups the question needs. Where the card renders,
the client can open any row as that instrument's full page. A figure that is
unknown is left out, never given as zero, and a line's note says why.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_ids": "<asset_ids>"
    },
    "name": "describe_assets"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No
`asset_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description spends its budget on behaviour it alone can explain: the 500-item cap, per-line output, null handling ('unknown is left out, never given as zero, and a line's note says why'), and client-side currency conversion. That is genuine predictive value beyond the annotation set.

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?

Front-loaded headline sentence states scale and shape, then the sibling relationship, then the payload, then the field groups. No sentence is redundant; the group list is compact given six enum values to explain.

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 no output schema, the description still specifies what comes back per row and how missing data is signalled (omitted, not zeroed, with an explanatory note) — exactly the ambiguity an agent would otherwise hit. Row ordering and behaviour on invalid/unknown ids are the remaining gaps.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden, and it does: `fields` is expanded into all six groups with what each contains (classification → ISIN/GICS/size/themes; growth → screener's score and its parts; esg → score and exclusion), far beyond the enum in the schema. `asset_ids` is scoped as up to 500 instruments or any id list. Only the id provenance is unstated.

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?

Names the specific verb/resource (headline figures per instrument), the scale (up to 500 in one call, one line each), and explicitly positions itself as 'the comparison form of describe_asset'. An agent can distinguish this from describe_asset and screen_equities without opening a schema.

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?

Gives concrete usage context ('for a screen's companies or any list of ids') and implicit routing away from the single-asset sibling via 'the comparison form of describe_asset'. It also advises 'Ask only for the groups the question needs', which is real field-selection guidance. No explicit when-not-to-use or pointer to where to obtain the ids, so not a 5.

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

All Analyzera tools Inspect

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

Need Help?