Skip to main content
Glama

Arcnin public information

get_documentation

Read-only

Use this when someone needs source documentation about the public API, desktop privacy, pricing, or support. Returns the published page as Markdown.

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": {
      "topic": "<topic>"
    },
    "name": "get_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhich published document to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-domain read. The description adds the useful return format detail (Markdown, the published page), but says nothing about page size, truncation, or what happens for an unavailable topic. With the safety profile already covered by annotations, this is adequate rather than rich.

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?

Two short sentences with zero waste: the usage trigger comes first, the return behavior second. Nothing is repeated from the schema or annotations.

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 one-parameter, read-only documentation lookup with no output schema, the definition covers what the tool does, when to reach for it, and what form the response takes. The only gap is sibling disambiguation, which matters given get_pricing sits nearby.

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% and the single parameter is a closed enum with its own description, so the schema carries the semantics. The description's topic list mirrors the enum values rather than adding selection guidance (e.g., which topic to pick for a mixed question), so baseline 3 is right.

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?

States a specific verb+resource: it retrieves published source documentation, and enumerates the exact subject areas (public API, desktop privacy, pricing, support) that it covers. An agent knows precisely what content comes back. It stops short of distinguishing itself from siblings such as get_pricing, which appears to touch the same 'pricing' subject.

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?

'Use this when someone needs source documentation about...' gives a clear triggering condition tied to the user's information need. It does not say when NOT to use it or point at an alternative, so an agent facing a pricing question must decide entirely from the topic list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources