Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Describe a tool

describe_tool
Read-only

Retrieve full descriptions and field-level guidance for Clipwright tools, including subfields, before first use to clarify inputs and avoid misconfigured calls.

Instructions

Free. tools/list gives each tool in short; this answers a tool's full description and every field's guidance, or one field's with its subfields. Read it before the first call of a tool or field you have not used, such as quote_ugc templates.

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": {
      "tool": "<tool>"
    },
    "name": "describe_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
fieldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.45.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real context beyond them: the operation is 'Free' (a cost property not expressed in annotations) and the granularity is either full-tool or single-field with subfields. It stops short of describing error behavior for an unknown tool or field name, which would be the remaining useful disclosure.

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 dense sentences, front-loaded with the cost qualifier and the sibling contrast before the usage instruction. Nothing is padding, though 'gives each tool in short' is grammatically awkward and slightly slows the read.

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?

No output schema exists, so the description must imply the return value, and it does: a full description plus every field's guidance, or one field's with subfields. For a two-parameter read-only meta-tool that is close to sufficient; only the failure mode for unrecognized tool/field names is left unspecified.

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 0%, so the description must carry parameter meaning. It does convey that 'tool' selects the tool to describe and 'field' narrows the answer to one field plus subfields, implicitly making field optional. It does not say whether the names must be exact identifiers from tools/list, nor what happens on a miss — gaps that matter for a free-text lookup parameter.

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?

Names a specific verb and resource ('describe_tool' — answers a tool's full description and every field's guidance) and explicitly contrasts itself with the sibling capability 'tools/list', which 'gives each tool in short'. An agent can tell the two apart without opening any schema.

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

Usage Guidelines5/5

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

States the trigger condition precisely: 'Read it before the first call of a tool or field you have not used', and gives a concrete example ('such as quote_ugc templates'). It also names the alternative (tools/list) and the condition that separates them, so routing is unambiguous.

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