Skip to main content
Glama
Sign In

HelpCenter.io

by io.helpcenter
OverviewDiscussionsAdmin

List HelpCenter Sites

helpcenter_list_sites
Read-onlyIdempotent

List the HelpCenter.io help centers this connection is allowed to reach, with their ids.

Call this FIRST when a tool fails with 'site_required', and whenever you are unsure which help center you are about to act on.

Why it exists: an OAuth connection authenticates a PERSON, and a person may have more than one help center. When neither the call nor the connection names one, the API refuses to guess and returns 'site_required' rather than acting on the wrong place. An API-key connection is bound to a single help center and will simply list that one.

How to act on the result: every other tool takes an optional site_id. When this list has more than one help center, pass the id of the one the user means as site_id on each call. It applies to that call only — nothing is remembered — so keep passing it, and use the same one for the whole task unless the user asks you to switch. If their request does not make clear which help center they mean, ask before you write anything. When the list has one help center, omit site_id.

Read-only, and unaffected by which help center a call names: it describes the connection, not a help center's contents.

Args:

  • response_format ('markdown' | 'json'): default 'markdown'.

Returns: { sites: [ { id, name, domain, ... } ] } — the help centers the credential's consent actually grants.

Errors: 401 if the credential is invalid or expired. An empty list from a valid OAuth token means the consent covered no site: the user has to re-authorize and pick one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "helpcenter_list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_formatNoOutput format: 'markdown' for a human-readable summary or 'json' for the full structured payload.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered; the description goes well beyond by explaining the OAuth-vs-API-key model, that nothing is remembered across calls, the 401 failure mode, and the meaning of an empty list (consent covered no site, re-authorize). That is exactly the kind of non-obvious behavior an agent cannot get from structured fields.

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 action and the trigger condition, then structured into why-it-exists, how-to-act, and returns/errors blocks. Slightly long, and the 'Args'/'Returns'/'Errors' headings duplicate schema-adjacent information, but nearly every sentence in the how-to-act block prevents a real misuse.

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?

No output schema, but the description supplies the return shape ({ sites: [{ id, name, domain }] }) and the error semantics, plus the operational rule that binds this tool to every other tool's optional site_id. For a one-parameter discovery tool in a 70+ tool surface, that covers everything needed 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% and the single parameter (response_format) is a documented enum with a default, so the schema carries the semantics. The description's 'Args' line largely restates it without adding format-selection guidance such as when to prefer json for programmatic chaining. Baseline 3 is appropriate.

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 ('List the HelpCenter.io help centers this connection is allowed to reach, with their ids') and immediately scopes it to the credential's grants. No sibling tool lists sites, and the description makes that uniqueness explicit by contrasting it with tools that act on a help center's contents.

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?

Gives concrete trigger conditions ('Call this FIRST when a tool fails with site_required', 'whenever you are unsure which help center you are about to act on') and explicit downstream behavior: pass site_id repeatedly when multiple sites, omit it when one, ask the user before writing if ambiguous. This is when/when-not guidance with an action recipe, not just context.

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

All HelpCenter.io 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