Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Start recording upload

create_recording_upload
Idempotent

Reserves storage for a recording before the in-chat recorder uploads it, ensuring a prepared destination for each take.

Instructions

Reserves storage for a take the in-chat recorder is about to upload. Called by the recorder itself.

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": {
      "origin": "<origin>",
      "content_type": "<content_type>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_recording_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
file_nameNo
account_idNo
content_typeYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description usefully clarifies that this only reserves storage rather than performing the upload, but says nothing about reservation lifetime, what happens on a duplicate idempotency key, or what the caller receives back.

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?

Two short, front-loaded sentences with no filler; the purpose arrives first and the caller constraint second. Brevity here shades into under-specification rather than wasted wording.

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?

For a non-read-only tool with five parameters at 0% schema coverage and no output schema, the description leaves critical gaps: no return value (upload URL, reservation id?), no parameter meanings, no error or expiry behavior. An agent could not reliably invoke this correctly from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and only account_id carries any inline documentation. The description does not explain origin, content_type, idempotency_key, or file_name at all, so it fails to compensate for the coverage gap on a five-parameter mutation.

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: it reserves storage for a recording take before upload. That is clearly distinct from sibling operations like finish_recording_upload or add_recording, though it never names them.

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?

'Called by the recorder itself' signals this is an internal/automated step rather than a general-purpose tool, which is useful routing context. It stops short of telling an agent when to call it manually, what the mandatory follow-up is, or what to do if a reservation already exists.

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