Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

upload_status

Read-only

Check a queued upload's status and progress using its task ID to monitor processing and determine when it completes.

Instructions

Check a queued upload's status and progress using its task ID.

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": {
      "task_id": "<task_id>"
    },
    "name": "upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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=true, so the safety profile is covered. The description adds only that the target is a 'queued' upload, without saying whether progress is a percentage, what status values exist, or whether the task ID expires — reasonable but thin additional context for a polling tool.

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 front-loaded sentence with no filler; the action, the object, and the required key all appear before the first clause ends.

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?

For a simple read-only polling call this is close to adequate, but with no output schema the agent gets no hint about the shape of returned status/progress, and the cursor parameter is unexplained. A sentence on what a completed vs. in-progress response looks like would close the gap.

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% with two parameters, so the description carries the burden. It clarifies only task_id (the upload task identifier); the cursor parameter is never mentioned, leaving its pagination role entirely opaque.

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?

The description names a specific verb and resource: check the status and progress of a queued upload, keyed by task ID. That is unambiguous on its own, though it does nothing to distinguish itself from any sibling (the listed siblings are unrelated dataset/catalog tools, so no confusion is likely).

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?

It implies the usage context (an upload was queued and you have a task ID) but gives no explicit when-to-use, when-not-to-use, or what to do once the task reports complete. The agent must infer the lifecycle position of this call.

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