Refapp Help

Read a Refapp help article

get_help_article

Read-onlyIdempotent

Returns one article from Refapp's help center as plain text, with its links. Accepts support.refapp.com knowledge-base links only.

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": {
      "url": "<url>"
    },
    "name": "get_help_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The article's link

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive and open-world profile, so the bar is lower. The description still adds value beyond them: the output is plain text with links preserved, and only support.refapp.com knowledge-base links are accepted, which tells the agent an out-of-domain URL will fail.

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, zero waste. The output shape is stated first and the input constraint second, in an order that lets an agent confirm fit quickly.

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 single-param read tool with full annotations, the description covers what it returns and what inputs are valid. It lacks detail on failure behavior for non-matching URLs or what happens with unreachable pages, a minor gap for an open-world fetch.

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% and the schema only says 'The article's link', so the description's domain restriction to support.refapp.com knowledge-base links meaningfully narrows the accepted value beyond structured data.

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 (Returns) and resource (one help-center article) plus the return format (plain text, with links). It doesn't explicitly name the sibling it complements (search_help) to find the link, so sibling differentiation is only inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Accepts support.refapp.com knowledge-base links only' establishes the precondition, implying the URL must come from a help-center source such as search_help. However, no explicit when-to-use or when-to-prefer-a-sibling guidance is given.

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

All Refapp 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?