Analyzera

Share a view

share_view

Idempotent

A public link to one card view, for WhatsApp, SMS, mail or Slack.

``kind`` picks what it shows:
- ``portfolio``: one dashboard tab (default 'returns') of strategy or account
  ``portfolio_id``. ``compare_id`` draws a market benchmark or another strategy
  beside it; ``lookthrough`` shows holdings with funds resolved. ``all_tabs`` shares
  every tab and ``allow_copy`` lets the viewer copy a strategy the client owns into
  their own account; both are on unless the client asks for one tab or no copying.
- ``comparison``: ``portfolio_id`` with ``against_id`` beside it, as
  ``open_dashboard`` with ``compare_id`` draws them.
- ``instruments``: one of ``asset_ids`` opens its page on ``tab`` (default
  'performance'); several open the table ``describe_assets`` draws.

The link opens the card fixed on that view, read-only, with live figures in weights
and percentages only, never values, amounts or units. The viewer cannot change the
client's account; a copy is the viewer's own. The same view reuses its link;
``revoke_share`` turns it off.

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": {
      "kind": "<kind>"
    },
    "name": "share_view"
  }
}

Input Schema

Name	Required	Description	Default
`tab`	No
`kind`	Yes
`all_tabs`	No
`asset_ids`	No
`against_id`	No
`allow_copy`	No
`compare_id`	No
`lookthrough`	No
`portfolio_id`	No

Output Schema

Name	Required	Description	Default
`say`	Yes	The same, as a sentence.
`link`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / $defs / CardTab / enum

Previous value: -[
-  "returns",
-  "weights",
-  "risk",
-  "fundamentals",
-  "outlook",
-  "construction",
-  "performance",
-  "tilts"
-]New value: +[
+  "returns",
+  "weights",
+  "risk",
+  "fundamentals",
+  "outlook",
+  "construction",
+  "performance",
+  "holdings",
+  "tilts"
+]

Changed3 schema fields changedNov 2, 2026

changedInput schema / $defs / CardTab / enum

Previous value: -[
-  "returns",
-  "weights",
-  "risk",
-  "fundamentals",
-  "outlook",
-  "performance",
-  "tilts"
-]New value: +[
+  "returns",
+  "weights",
+  "risk",
+  "fundamentals",
+  "outlook",
+  "construction",
+  "performance",
+  "tilts"
+]

changedInput schema / properties / all_tabs / default
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / allow_copy

Added value: +{
+  "default": true,
+  "title": "Allow Copy",
+  "type": "boolean"
+}

First observedOct 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: the link is read-only and fixed on that view, shows live figures in weights and percentages only, never values/amounts/units, and 'the viewer cannot change the client's account; a copy is the viewer's own.' It also discloses link reuse and that revoke_share disables it. No contradiction with readOnlyHint=false, since creating a link is a mutation.

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?

Front-loaded one-line purpose followed by per-kind bullets, with no filler sentences. The nested sub-clauses in the portfolio bullet are dense but each clause maps to a parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter sharing mutation with an output schema present, the description covers scope, per-parameter meaning, defaults, disclosure limits, and reversal via revoke_share. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 0%, so the description must carry all nine parameters, and it does: kind, portfolio_id, compare_id, lookthrough, all_tabs, allow_copy, against_id, asset_ids and tab are each given meaning plus defaults (tab 'returns', all_tabs/allow_copy on unless…). This exceeds what the bare schema conveys.

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?

Opens with a specific verb and resource: 'A public link to one card view' for WhatsApp, SMS, mail or Slack. The three 'kind' values are each given a distinct meaning, so an agent can tell what it produces without opening the 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?

Each 'kind' is given a concrete selection rule (portfolio = one dashboard tab, comparison = portfolio_id with against_id, instruments = asset_ids on tab), and it names 'revoke_share' for turning the link off. It does not state when *not* to share or contrast against a sibling like list_shares, which keeps it from 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?