Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Create Portfolio Snapshot

create_portfolio_snapshot

Capture an immutable rollup of YOUR OWN ticket portfolio, or one owned ProjectWorkspace when project_id is supplied, as it stands right now -- totals by status and priority, fixed at this moment and never recomputed. A snapshot is the durable 'here is where we were' that a later diff_portfolio_snapshots measures movement against, so capture one before a review rather than after. Snapshots cannot be edited or deleted once taken. The snapshot records the credential that captured it, so one taken by an agent is attributable as such. Requires authentication and the tickets:write scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional human label, e.g. the review it was taken for. Omitted leaves the snapshot unlabelled.
project_idNoOwned ProjectWorkspace UUID from project_list. Omit for the whole portfolio.
request_idNoReuse this UUID and the exact label/project scope to recover an uncertain capture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Owned ProjectWorkspace UUID from project_list. Omit for the whole portfolio.",
+  "format": "uuid",
+  "type": "string"
+}
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Reuse this UUID and the exact label/project scope to recover an uncertain capture.",
+  "format": "uuid",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only tell us it is a non-destructive write; the description adds substantial context beyond that: immutability, no recompute, cannot be edited or deleted, records the capturing credential for attribution, and requires auth plus the tickets:write scope. This is rich disclosure the structured fields do not carry.

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?

Four sentences, front-loaded with the core action and scope, then rationale then immutability then auth. Every sentence earns its place, though the immutability point is restated ('fixed at this moment and never recomputed' plus 'cannot be edited or deleted'), which is minor redundancy.

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?

There is no output schema, but the description explains what a snapshot contains (totals by status and priority) and the lifecycle constraints an agent must know before calling. Nothing needed to invoke it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented. The description reinforces the project_id scope semantic (single project vs whole portfolio) but adds no format or syntax details beyond the schema, so the baseline 3 is appropriate.

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 (capture) and resource (immutable rollup snapshot) plus scope distinctions: YOUR OWN portfolio vs a single owned ProjectWorkspace when project_id is supplied. It names the sibling diff_portfolio_snapshots and its relationship, so an agent can distinguish this from list/get/create_note/export siblings.

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 timing guidance ('capture one before a review rather than after') and explains the alternative it pairs with (diff measures movement against a prior snapshot). It also routes scope selection (project_id vs whole portfolio), leaving little to inference.

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