Skip to main content
Glama
Sign In
ponisha-mcp

ponisha-mcp

by Kia-Karami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ponisha_upload_file

Uploads a local file for a Ponisha portfolio item and returns its file_id, choosing portfolio content or a preview cover image.

Instructions

Upload a file from this computer for a portfolio item and get its file_id. kind portfolio (jpg, png, gif, mp4, pdf, mp3, wav; up to 10 MB) is for the item's contents; portfolio_preview (jpg, png; up to 5 MB) is for the cover image (preview_image). Uploading alone changes nothing visible on your profile.

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": {
      "file_path": "<file_path>"
    },
    "name": "ponisha_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoportfolio
file_pathYesAbsolute path to a local file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, open-world call; the description adds real value by disclosing per-kind size limits, allowed formats, and the side-effect boundary (nothing visible changes until the id is used). Auth requirements and server-side failure modes are not covered.

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?

Purpose is front-loaded in the first sentence, then constraints, then the caveat; every clause carries information. The parenthetical format/size lists are dense but readable.

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?

For a two-parameter upload with no output schema, the description covers purpose, the returned file_id, per-kind limits, and the visibility caveat. A note about authentication or whether re-uploads duplicate storage would round it out.

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 50% (only file_path is documented, kind is a bare enum), and the description fully compensates by defining both kind values, their intended use, accepted formats and size caps. It adds little for file_path beyond what the schema already says.

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 ("Upload a file from this computer for a portfolio item") and names the direct output (file_id), so an agent can distinguish it from the portfolio CRUD siblings like ponisha_create_portfolio.

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 clearly explains which of the two modes to use for what purpose (item contents vs cover image) and warns that "Uploading alone changes nothing visible on your profile," implying a follow-up step. It does not name the specific sibling (create/update portfolio) that consumes the file_id, keeping it short of a 5.

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

Deploy Server

Other Tools