Digital Help

Run a DigitalHelp tool by slug

run_tool

Run a tool by the slug search_tools returned (callable: true) and get its result plus a link to its page. Runs paga-neto (same as calculate_net_salary) and krijo-cv (same as create_cv); input takes the same fields as that tool. Any other slug returns only the page URL to share with the user. Regional tools need region. Calculators only compute; krijo-cv saves the CV draft for 60 minutes behind a one-time link.

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": {
      "slug": "<slug>",
      "input": "<input>"
    },
    "name": "run_tool"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Tool slug from search_tools, e.g. "paga-neto".
`input`	Yes	The tool's input fields, as in the matching named tool's input schema.
`locale`	No	Language of titles, descriptions and page links.	en
`region`	No	Required for regional tools: al = Albania, xk = Kosovo.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / input / description

Previous value: -"The tool's input fields, matching the inputSchema search_tools returned for it."New value: +"The tool's input fields, as in the matching named tool's input schema."

changedInput schema / properties / locale / description

Previous value: -"Language of titles and descriptions."New value: +"Language of titles, descriptions and page links."

First observedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare non-read-only, non-destructive, and non-idempotent behavior. The description adds important context beyond annotations: calculators only compute, krijo-cv saves a CV draft for 60 minutes behind a one-time link, and unsupported slugs return only a shareable page URL.

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 four tight sentences. The core run-and-return behavior is front-loaded, followed by exceptions and side-effect details, with no filler or repetition.

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 dynamic wrapper with nested input and no output schema, it explains the result (tool output plus page link), fallback URL-only behavior, regional requirements, and CV draft lifetime. This 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 baseline is 3. The description adds cross-tool meaning for slug (from search_tools, callable:true), input (same fields as the corresponding named tool), and region (required for regional tools), though it adds little for locale beyond 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?

States a specific verb ('Run') and resource ('a tool by slug'), identifies the slug source as search_tools with callable:true, and names sibling equivalents: paga-neto/calculate_net_salary and krijo-cv/create_cv. This clearly distinguishes run_tool from search_tools and the named tools.

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?

Explicitly says to use slugs returned by search_tools that are callable:true, notes that paga-neto and krijo-cv mirror the named tools, and states that any other slug only returns a page URL. It also notes regional tools require region, covering when to use it and what happens otherwise.

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

All Digital Help 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?