GetSign MCP

getsign_help

Read-onlyIdempotent

Read GetSign agent docs or named flow recipes. Do not use this to list tools.

    tools/list already has every tool name and description. This tool is for
    on-demand guides — remote MCP clients do not get local CLAUDE.md.

    No args: short index of doc paths and flow names.
    path: markdown for that guide (gotchas, placeholders-and-signers,
    flows/send_new_document, or a getsign://docs/... URI).
    flow: same as path=flows/{name} (e.g. send_new_document).
    query: matching docs, flows, and related tool names — not the full catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`flow`	No
`path`	No
`query`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 18, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description is consistent. It adds valuable behavioral context beyond annotations: no args returns a 'short index', path returns markdown, flow is an alias, and query returns 'matching docs, flows, and related tool names — not the full catalog.' This discloses output scope and limitations clearly.

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?

The description is efficiently structured: a one-line purpose, an exclusion warning, then a concise bullet-like breakdown of modes. Every sentence earns its place, and the most important context (what the tool does and does not do) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only help tool with three optional parameters, the description is complete: purpose, when-not-to-use, alternative tool, parameter behavior, examples, and return behavior for no args. The output schema exists, so detailed return format is not needed in the description. An agent has everything necessary to select and call this tool correctly.

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

Parameters5/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 fully compensate, and it does. Each parameter (path, flow, query) is explained with concrete examples, including valid path forms like 'flows/send_new_document' and 'getsign://docs/...'. This makes the parameters actionable without schema descriptions.

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 opens with a specific verb and resource: 'Read GetSign agent docs or named flow recipes.' It immediately differentiates from listing tools by saying 'Do not use this to list tools' and clarifies that tools/list covers tool names and descriptions. This makes the tool's role unmistakable among the many getsign_* siblings.

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?

Provides explicit exclusion guidance: 'Do not use this to list tools. tools/list already has every tool name and description.' It also explains when this tool is appropriate ('on-demand guides') and why it exists ('remote MCP clients do not get local CLAUDE.md'). Each parameter mode is described, leaving no ambiguity about how to invoke it.

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

All GetSign MCP 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.

Resources

Need Help?