GravityPort

generation_list

Read-only

List generation occurrences to track AI library activity. Filter results by output asset, capture context, or provider call identifiers.

Instructions

List generation occurrences, optionally filtered by output asset or provider identifiers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generation_list"
  }
}

Input Schema

Name	Required	Description	Default
`assetId`	No
`captureContextId`	No
`providerToolCallId`	No
`providerGenerationCallId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.11Nov 11, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that filtering is optional and what kinds of identifiers can filter, with no disclosure of pagination, result caps, or return shape — modest value beyond annotations.

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?

A single front-loaded sentence with no filler; the optional-filtering qualifier is placed correctly after the core action. It is efficient, though it spends its limited space on a vague phrase ('generation occurrences') rather than precise semantics.

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

Completeness2/5

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

For a four-parameter list tool with no output schema and zero schema coverage, the description leaves too much unexplained: one parameter is never referenced, filter combination behavior is unknown, and what a 'generation occurrence' contains is never stated. An agent could call it, but could easily mis-target its filters.

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

Parameters2/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 parameter meaning, yet it only loosely gestures at 'output asset' (likely assetId) and 'provider identifiers' (likely the two provider call IDs). captureContextId is entirely unmentioned, and no format, matching semantics, or combinability of filters is explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'List generation occurrences,' which is distinguishable from siblings like generation_record or generation_lineage. It does not explicitly contrast itself with those siblings, and 'generation occurrences' remains somewhat jargon-dependent, but the core action is unambiguous.

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

Usage Guidelines2/5

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

The word 'optionally' implies you may call it with no filters to get everything, but there is no explicit when-to-use guidance and no mention of when to prefer generation_record or generation_lineage instead. An agent must infer the selection logic from names alone.

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