varg how to

Read a varg how to page

get_how_to

Read-onlyIdempotent

Read one varg how to card in full as Markdown: a how-to tutorial (best skills with install commands, the options to show the person with example videos, the steps, how it runs on varg) or a skill, component or video type page. Pass the kind and slug from search_how_to.

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": {
      "kind": "<kind>",
      "slug": "<slug>"
    },
    "name": "get_how_to"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	The card's kind, exactly as search_how_to returned it (usually how_to).
`slug`	Yes	The card's slug, exactly as search_how_to returned it, e.g. make-a-lyric-video.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedInput schema / properties / kind / description

Added value: +"The card's kind, exactly as search_how_to returned it (usually how_to)."

addedInput schema / properties / slug / description

Added value: +"The card's slug, exactly as search_how_to returned it, e.g. make-a-lyric-video."

First observedOct 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), and the description adds the one thing they cannot: the response format is full Markdown content rather than a summary or record. It doesn't discuss failure behavior for bad kind/slug pairs, but that is a modest gap given the annotations.

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?

One front-loaded sentence carries the action and the return format, followed by a short routing instruction. The parenthetical enumeration of tutorial contents is somewhat long but still earns its place by telling the agent what a full read contains.

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, idempotent read with no output schema, the description supplies what matters: the return is complete Markdown and inputs must come verbatim from a prior search. Nothing essential is absent, though a note on not-found or invalid kind behavior would round it out.

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 coverage is 100% and both parameters are already documented as "exactly as search_how_to returned it," including an enum for kind and a slug example. The description's contribution is repeating the provenance hint, which adds no syntax or meaning beyond the schema — baseline 3.

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 and resource ("Read one varg how to card in full as Markdown") and enumerates the card varieties it covers (how-to tutorial, skill, component, video type page). The sibling relationship is explicit: values come from search_how_to, so an agent can tell retrieval from lookup without opening a schema.

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?

The description makes the workflow clear by instructing "Pass the kind and slug from search_how_to," which implies this is the follow-up call to a search result. It stops short of explicitly stating when not to use it or what happens on a miss, but the context is unambiguous for a lookup tool.

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

All varg how to 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?