Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Read a Privatrak docs page

read_docs_page
Read-onlyIdempotent

One page of Privatrak's documentation as Markdown, in full, with its title and URL. page is a slug such as no-code-tracking, or a docs URL from search_docs; an unknown page answers with the valid slugs. Use it when a search_docs snippet is not enough, and to follow the documented instructions (tracker attributes, framework setup) exactly instead of recalling them. Quote the URL when pointing the user there.

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": {
      "page": "<page>"
    },
    "name": "read_docs_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the docs: en (default) or de. A /de/ URL means de when lang is not given.
pageYesThe page: a slug such as no-code-tracking, a path such as /docs/no-code-tracking, or a docs URL as returned by search_docs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-openWorld, so the safety profile is covered. The description adds genuinely new behavior: an unknown page returns the valid slugs, and content is returned in full with its title and URL. It does not mention rate limits or payload size, which keeps it short of a 5.

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?

Front-loaded with the return shape, then usage, then a short operational tip about quoting the URL. Dense but every sentence carries information; slightly long with four clauses in the final sentence.

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?

With no output schema, the description carries the return-value burden and does so (Markdown, title, URL), plus the unknown-page fallback. A minor gap remains around how lang interacts with page, but the agent has enough to call it correctly.

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 100%, so both parameters are already documented, including the lang enum-by-convention. The description restates the accepted page forms (slug, path, docs URL) and gives an example slug, adding only marginal value beyond the schema. Baseline 3 applies.

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 Privatrak docs page) and immediately describes what comes back: full Markdown plus title and URL. It is clearly distinguishable from search_docs, which returns snippets.

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 routes the agent: 'Use it when a search_docs snippet is not enough,' and further says to follow documented instructions exactly rather than recalling them. This is a clear when-to-use rule tied to a named alternative.

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

All Privatrak 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