Skip to main content
Glama

PortfolioFit

Cancel portfolio series upload

cancel_portfolio_series_upload
DestructiveIdempotent

Cancel a pending upload and permanently remove its staging chunks.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "cancel_portfolio_series_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes
analysis_nameNoOptional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calculation still needs its own idempotency_key.

Output Schema

NameRequiredDescriptionDefault
statusYes
upload_idYes
analysis_idYes
analysis_urlYes
cancelled_atYes
analysis_nameYes
staging_deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuine value by specifying what is destroyed ('its staging chunks') and that removal is permanent. It still omits idempotency/retry behavior and any permission requirements.

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?

A single sentence with the verb, precondition, and destructive effect front-loaded. No filler, nothing redundant with the title.

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

Completeness3/5

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

An output schema exists and annotations cover the safety profile, so return values and destructive semantics need not be restated. However, for a destructive mutation the description leaves real gaps: what happens on an already-completed or already-cancelled upload, whether the analysis_name group is affected, and what the response confirms.

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?

The description says nothing about either parameter. Schema coverage is only 50%: analysis_name carries a rich schema description, but upload_id is undocumented in both schema and description, and the description does not compensate for that gap.

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?

Specific verb (cancel) plus a precise resource and scope ('a pending upload') with the side effect stated, so an agent can distinguish it from upload_portfolio_series_rows and the read-oriented list/review siblings. It stops short of naming any sibling explicitly, so it lands just below the top band.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'pending', which suggests the upload must still be in flight, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g. what to do for a completed upload). No error-state or prerequisite guidance is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources