Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Diff Portfolio Snapshots

diff_portfolio_snapshots
Read-onlyIdempotent

Compare two of your own portfolio snapshots and return the per-dimension movement between them. snapshot_id is always the 'to' side; against is the 'from' baseline, defaulting to your newest snapshot in the same project or portfolio strictly older than it -- the 'what changed since last time' read, which is reported as not found when this is your first snapshot. Comparing an older snapshot against a newer one is allowed and disclosed rather than silently confusing: the result says whether the pair is chronological and the elapsed days go negative. Both sides are immutable, so a diff is reproducible indefinitely. Requires authentication and the tickets:read scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
againstNoThe baseline to compare against -- the 'from' side. Omit for your newest snapshot older than snapshot_id.
snapshot_idYesThe snapshot being examined -- the 'to' side, from list_portfolio_snapshots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses immutability and indefinite reproducibility, the tickets:read scope and auth requirement, the not-found outcome for a first snapshot, and the negative-elapsed-days behavior on reversed pairs. This is substantial context an agent could not infer from annotations alone.

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-loads purpose then layers the defaulting rule, edge cases, and reproducibility. Slightly dense and one clause ('allowed and disclosed rather than silently confusing') is wordier than needed, but every sentence carries actionable information.

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?

With no output schema, the description still conveys what a result contains (per-dimension movement, chronological flag, elapsed days) plus auth, scope, and immutability constraints. Nothing an agent needs to invoke or interpret the tool is missing.

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 100%, so the schema already documents both parameters. The description nonetheless adds meaning by clarifying the 'to' vs 'from' roles and the exact default-resolution rule for 'against' (newest snapshot strictly older in the same project or portfolio), which goes beyond the schema text.

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?

States a specific verb and resource ('Compare two of your own portfolio snapshots') and names the output ('per-dimension movement between them'). It is clearly distinguishable from siblings like get_portfolio_snapshot (single read) and list_portfolio_snapshots (enumeration).

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?

Explains the primary use case ('what changed since last time'), the default-resolution behavior when 'against' is omitted, the first-snapshot not-found case, and that reversed chronological comparisons are permitted. It does not explicitly route to a specific alternative sibling, but the usage context is unambiguous.

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

All Meta Council 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