Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Upload image

upload_image

Uploads a local image file (JPEG, PNG, WebP, or GIF) to the Misar.Blog CDN for use in blog content.

Instructions

Upload a local image file to the Misar.Blog CDN

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

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the image file (JPEG, PNG, WebP, or GIF)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv5.1.3
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute path to the image on this machine, e.g. '/Users/me/cover.png'. JPEG, PNG, WebP or GIF; the type is inferred from the extension."New value: +"Absolute path to the image file (JPEG, PNG, WebP, or GIF)"
  3. Changed1 schema field changedv5.1.0
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute path to the image file (JPEG, PNG, WebP, or GIF)"New value: +"Absolute path to the image on this machine, e.g. '/Users/me/cover.png'. JPEG, PNG, WebP or GIF; the type is inferred from the extension."
  4. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-idempotent, open-world, non-destructive write, so the safety profile is covered. The description adds the meaningful detail that the source is a local file and the destination is a remote CDN, but omits authentication requirements, size/format limits beyond the schema, overwrite behavior, and any rate limits. For a mutation with external side effects, a 3 is fair given the annotation coverage.

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?

A single front-loaded sentence with zero wasted wording. It is arguably too terse for a mutation tool, but nothing in it is redundant.

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?

There is no output schema, so the description should explain what the call returns — most critically the resulting CDN URL, which an agent would need to reference the image elsewhere (e.g. in publish_article). It also says nothing about authentication or failure modes, leaving real gaps for a write tool with external effects.

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?

The schema has 100% description coverage on the single parameter, documenting the absolute path and accepted formats, so the description carries no extra burden. It also adds nothing beyond the schema, which puts it at the baseline.

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?

States a specific verb and resource ('Upload a local image file') plus the destination ('Misar.Blog CDN'), which is clear and actionable. It does not differentiate from the sibling 'generate_cover_image', so an agent must infer that this tool handles pre-existing local files rather than generated images.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as generate_cover_image for creating imagery versus uploading it. The only implicit signal is the phrase 'local image file', which the reader must interpret as the selection criterion.

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