Skip to main content
Glama

Upload text asset

upload_text_asset
Destructive

Save explicitly supplied research text as an artifact in an authorized project. Identifiable patient data is prohibited.

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": {
      "content_text": "<content_text>",
      "project_id": "<project_id>",
      "filename": "<filename>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "upload_text_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
folder_idNo
media_typeNotext/plain
project_idYes
content_textYes
idempotency_keyYesOne UUID retained for this logical mutation and its retries.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds two genuinely useful pieces of context beyond them: the target must be an authorized project, and identifiable patient data is prohibited. However, it never explains the destructive profile — e.g. whether uploading with an existing filename overwrites or fails — even though that is the single most consequential behavior for a tool annotated destructive. With annotations present, a 3 is appropriate: it adds value but leaves the risky behavior undisclosed.

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, zero padding, with the core action front-loaded and the compliance constraint immediately after. Nothing is redundant, though the brevity is also what leaves the gaps noted elsewhere.

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 multi-parameter mutation with destructiveHint=true and only 17% schema coverage, the description is thin: no overwrite/collision semantics, no size or format limits for content_text, no explanation of how folder_id or media_type affect placement. An output schema exists, so return values needn't be described, but the input-side and risk-side gaps are significant.

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 only 17%, with just idempotency_key documented, so the description would need to carry the other five parameters. It gives only loose mapping ('research text' → content_text, 'authorized project' → project_id) and says nothing about filename, folder_id, or media_type (default text/plain). The partial mapping keeps it above a 1, but the compensation is far from adequate.

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 gives a specific verb and resource: 'Save explicitly supplied research text as an artifact in an authorized project.' An agent can tell this creates an artifact from caller-provided text, and the phrase 'explicitly supplied' distinguishes it from tools that fetch or extract content themselves. It stops short of naming a sibling (e.g. import_evidence) it is meant to be chosen over.

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?

The 'explicitly supplied research text' constraint implies usage context (the agent must already hold the text rather than have the tool retrieve it), and 'authorized project' hints at a prerequisite. But there is no explicit statement of when to prefer this over import_evidence or other artifact-producing tools, and no exclusions.

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