Skip to main content
Glama

Get Knowledge Upload

get_knowledge_upload
Read-onlyIdempotent

Where a create_knowledge_upload stands: the bytes received, then the document it became and its processing state (a recording is ready once transcribed; read_knowledge_document gives the text). Pass the same app_id the upload was made with.

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": "get_knowledge_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idNoOptional app whose notebooks to use. Omitted: the owner's own Business Brain.
upload_idYesThe upload_id create_knowledge_upload returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that by describing the response shape (bytes received, document created, processing state) that the agent otherwise could not know, since there is no output schema. Polling/retry behavior over time is implied but not spelled out.

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?

Two sentences and a parenthetical, with no filler; the parenthetical about transcription readiness earns its place. The inverted opening ('Where a create_knowledge_upload stands') is slightly awkward and delays the point, keeping it short of ideal front-loading.

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

Completeness4/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 carries the return-value burden and does so competently by naming the three things an agent will see. It is nearly complete for a two-parameter read tool; the only gap is guidance on polling cadence or terminal states beyond the transcription example.

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%, establishing a baseline of 3, and the description goes beyond it by constraining app_id: it must be the same app the upload was made with, which the schema only loosely calls 'optional app whose notebooks to use'. That consistency requirement is a genuine addition rather than a restatement.

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?

The description states a specific resource and verb-equivalent ('Where a create_knowledge_upload stands') and enumerates what is returned: bytes received, the resulting document, and its processing state. It distinguishes itself from create_knowledge_upload (which starts the upload) and from read_knowledge_document (which gives the text once ready).

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?

It gives a clear readiness rule ('a recording is ready once transcribed') and routes the agent to read_knowledge_document for the text, which is explicit alternative-routing. What it lacks is an explicit when-not or a statement that this is meant to be polled after create_knowledge_upload, which the agent must infer from the phrasing.

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