Ssemble AI Clipping

get_status

Check processing status of a short creation request. Provide a request ID, or omit it to see your recent requests and pick one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_status"
  }
}

Input Schema

Name	Required	Description	Default
`requestId`	No	The request ID from create_short (24-char hex). Omit to see your recent requests.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedApr 2, 2026

changedInput schema / properties / requestId / description

Previous value: -"The request ID from create_short (24-char hex)"New value: +"The request ID from create_short (24-char hex). Omit to see your recent requests."

removedInput schema / required
```
Removed value: -[
-  "requestId"
-]
```

First observedMar 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the read-only nature via 'Check' and the optional behavior of listing recent requests. It could mention output details but is adequate for a status check.

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?

Two sentences, both purposeful: the first states the action, the second gives usage instructions. No unnecessary words or repetition.

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?

The tool is simple with one optional parameter and no output schema. The description covers the main purpose and usage adequately, though it doesn't describe the response format. Given the low complexity, this is sufficient.

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% and the schema already fully describes requestId including the pattern and the omit behavior. The description adds minimal new meaning ('pick one') beyond what is already in the schema.

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 uses a specific verb 'Check' and identifies the resource as 'processing status of a short creation request'. This clearly distinguishes it from sibling tools like create_short, delete_request, and get_shorts.

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 provides clear context on how to use the tool: provide a request ID or omit it to see recent requests. It implies the workflow but does not explicitly state alternatives or when not to use it.

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

All Ssemble AI Clipping tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.