Skip to main content
Glama

Get Upload Command

get_upload_command
Read-onlyIdempotent

Generates a curl command to upload a genome file to the OpenPGx server, returning a code to use with load_profile for pharmacogenomic analysis.

Instructions

Returns a ready-to-run curl command that uploads a genome file directly to the OpenPGx server. Execute this command in your code execution sandbox or tell the user to run it in their terminal. The command sends the file WITHOUT reading it into context. After running it, use load_profile with the returned code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the genome file (e.g., /uploads/genome.txt or the path shown in the user's message)
Behavior5/5

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

Discloses that the command does not read the file into context, which is critical and beyond annotations. No contradictions with annotations (readOnlyHint=true, idempotentHint=true).

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?

Three concise sentences covering what, how, and next steps. No fluff, every sentence earns its place.

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

Completeness5/5

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

Given no output schema, description adequately explains the return value (curl command with code) and the subsequent tool to use. Sufficient for a simple tool.

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 coverage is 100% with adequate description. Tool description does not add new semantic meaning beyond the schema, meeting baseline but not exceeding.

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?

Clearly states it returns a curl command to upload a genome file. Distinguishes from sibling upload tools by specifying it returns a command string rather than performing the upload directly.

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?

Provides execution instructions (sandbox or user terminal) and next step (use load_profile). Lacks explicit comparison to sibling upload tools like upload_genome, but usage is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/open-pgx/openpgx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server