Skip to main content
Glama
TherapyPortal MCP Server

TherapyPortal MCP Server

by chrischall

therapyportal_upload_slot

Read-only

Get a signed upload URL for one allowed file, PUT the file bytes with the returned Content-Type before expiry, then call the document upload tool with the blob key.

Instructions

Hosted servers: get a signed upload URL for ONE file you then upload with therapyportal_upload_document. Sends nothing to the practice. PUT the file’s bytes to uploadUrl with the returned Content-Type (the returned curl does exactly that; replace its <path to …> placeholder), then call therapyportal_upload_document with blob_key. The URL expires at expiresAt. Same file rules as the upload: PDF, JPG, JPEG, PNG, HEIC or DOCX, up to 25 MB, a bare filename; .doc is refused.

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": {
      "filename": "<filename>"
    },
    "name": "therapyportal_upload_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesThe name the practice will see — a bare name with its extension, e.g. "scan.pdf".
mime_typeNoOptional; must agree with the extension. Default: from the extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: the tool sends nothing to the practice, returns an uploadUrl and Content-Type, expires at expiresAt, and requires a subsequent upload_document call. It also explains the exact HTTP PUT step and the curl placeholder replacement, which prevents common invocation errors. The readOnlyHint=true annotation is consistent with a tool that only obtains a URL and does not mutate practice data.

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?

The description is front-loaded with the core purpose and then proceeds through the exact multi-step workflow. Every sentence carries operational value: the no-practice-send warning, the PUT instructions, the expiry behavior, and the file rules. The parenthetical about the returned curl is useful rather than redundant.

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?

There is no output schema, so the description appropriately explains the returned uploadUrl, Content-Type, blob_key, and expiresAt. It also covers file constraints and the required follow-up call, making the tool usable without additional documentation. The only omitted details, such as authentication mechanics, are not essential for correct invocation.

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%, so the baseline is 3, but the description adds meaningful constraints beyond the schema: allowed formats (PDF, JPG, JPEG, PNG, HEIC, DOCX), a 25 MB limit, bare filename requirement, and refusal of .doc. These constraints directly affect the supplied filename and MIME type. It does not add much beyond the schema for the optional mime_type parameter itself, which keeps this from a 5.

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 verb and resource: get a signed upload URL for exactly one file, then upload it via therapyportal_upload_document. It clearly distinguishes this preparatory step from the sibling tool that performs the actual document upload. An agent can identify the tool's role without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit workflow: call this tool first, PUT the file bytes to uploadUrl with the returned Content-Type, then call therapyportal_upload_document with blob_key. The sequencing and the warning that this tool sends nothing to the practice make the when-to-use guidance unambiguous. It also names the follow-up tool needed to complete the upload.

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