Skip to main content
Glama

get_clip

Read-onlyIdempotent

Un clip entero, con su texto completo en markdown, el resumen y los puntos clave.

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": {
      "clip_id": "<clip_id>"
    },
    "name": "get_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYesID del clip (de get_clips)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing what the call actually returns (full markdown text, summary, key points) — important here because there is no output schema. It does not describe truncation, size limits or failure behavior, keeping it below a 5.

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 tight sentence that front-loads the resource and enumerates the payload components without filler. It is perhaps slightly over-spare for a tool whose return shape is undocumented elsewhere, but nothing is wasted.

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 simple two-parameter read with full schema coverage and complete annotations, the description supplies the missing piece — what content comes back. Absent any mention of very large clips or error cases, it is complete enough to invoke correctly but not exhaustive.

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 description coverage is 100%: clip_id explicitly says it comes from get_clips, and workspace_id explains UUID-or-name matching plus the omit-equals-all semantics. The description adds no parameter meaning of its own, 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 states a specific resource and scope: a single complete clip ('un clip entero') with its full markdown text, summary and key points. That implicitly distinguishes it from the plural list tool get_clips, though the distinction is never made explicit by name, so it stops short of a 5.

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?

There is no guidance on when to use this rather than get_clips or the document/artifact retrieval siblings. The only routing help present ('Omitir = TODOS los workspaces') lives in the input schema, not the description, so the description itself offers no use conditions or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources