Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Send a photo

send_conversation_photo
Destructive

Queues a photo for delivery to a specific conversation using a local file path, enabling image sharing through the API.

Instructions

Send a photo. Required API key scope: conversations:write. POST /conversations/{id}/photo Queues a photo send; the message appears in the conversation once the worker delivers it.

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

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.
file_pathYesPath to a local file, uploaded as the multipart `photo` field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the required API key scope (conversations:write), the underlying HTTP route, and crucially that the send is queued and only appears in the conversation after a worker delivers it. That async behavior is real context an agent needs when verifying results. It does not, however, explain why destructiveHint is true or whether a queued send can be cancelled.

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?

Three compact lines, front-loaded with the action, then scope, then endpoint, then async note; nothing is padded. The opening "Send a photo." largely repeats the title, which is the only wasted word.

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 write tool with no output schema, the definition covers what the agent needs: auth scope, route, and post-call delivery semantics. Minor gaps remain around accepted image formats/size limits and an explicit statement that `id` is the conversation identifier.

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%, so both parameters are already documented, including that file_path is uploaded as the multipart `photo` field. The description adds no extra syntax, format, or size constraints beyond what the schema states, so the baseline of 3 applies.

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 uses a specific verb and object ("Send a photo") and pins it to the endpoint POST /conversations/{id}/photo, so the target resource is unambiguous. It does not explicitly distinguish itself from the sibling send_conversation_reply (new message vs. reply), leaving that inference to the endpoint path.

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?

Usage is implied by the resource path and the required scope, but the description never states when to choose this over send_conversation_reply or other conversation tools, and lists no prerequisites beyond the API scope. Adequate but no explicit routing guidance.

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