Skip to main content
Glama
Sign In

Docmint

by io.github.Noju-io
OverviewDiscussionsAdmin

Get a Docmint link with settings preset

get_tool_link
Read-onlyIdempotent

Build a link to one Docmint tool with its settings filled in, such as compress-pdf with level=strong or split-pdf with mode=range and ranges=1-3. The person opens the link and adds the file in their browser, where it is processed on their device. Settings a tool doesn't accept are ignored and listed in the result. This tool only builds the link: it does not receive or process the file.

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": "get_tool_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool id, e.g. compress-pdf.
settingsNoTool settings by name. See find_pdf_tool or list_pdf_tools for each tool's settings and allowed values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses important behavior: unknown or unsupported settings are ignored and listed in the result, and the file is processed client-side rather than by this tool. It does not describe the exact return shape, such as whether the link is a string or an object with warnings, leaving a minor gap.

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 front-loaded with the core action, then adds examples, the browser handoff behavior, the unsupported-settings rule, and the scope boundary. Every sentence contributes distinct information, and there is no wasted wording.

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 two-parameter tool with full schema coverage and no output schema, the description covers the essential model: build a link, pass tool-specific settings, unsupported settings are ignored, and no file is processed here. It could be slightly more complete by stating the shape of the returned link or result, but it is sufficient for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters, but the description adds useful meaning by showing concrete settings examples like 'level=strong' and 'mode=range' with 'ranges=1-3.' It also explains that settings a tool does not accept are ignored and reported in the result, which is validation behavior not captured by the schema.

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 gives a specific verb and resource: 'Build a link to one Docmint tool with its settings filled in,' and reinforces scope with 'This tool only builds the link: it does not receive or process the file.' It does not explicitly distinguish this from the lookup siblings find_pdf_tool and list_pdf_tools, so it stops short of the top score.

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 clearly describes the intended handoff scenario: a person opens the link, adds the file in their browser, and processing happens on their device. It also states a when-not boundary by saying the tool does not receive or process the file. It stops short of naming alternatives or explicitly directing the agent to find_pdf_tool/list_pdf_tools for settings discovery.

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

All Docmint toolsInspect
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