Skip to main content
Glama
Sign In
Concrete CMS MCP Server

Concrete CMS MCP Server

by concrete5-community
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_connection

Read-only

Checks a Concrete CMS site's reachability and connector setup, including API access, auth headers, client ID, redirect URI, and scopes. Use it to troubleshoot connection or authorization errors.

Instructions

Check that this connector can work with the Concrete CMS site: site reachable, pretty URLs, API enabled, Authorization header, and the Client ID, Redirect URI and scopes of the API integration. It needs no sign-in. Use it when the user asks to check or troubleshoot the connection, or when the other tools fail with connection or authorization errors. Every failed check comes with how to fix it.

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": "check_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A4.6/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuinely new behavior: it performs a multi-point diagnostic rather than a single fetch, requires no authentication, and returns remediation guidance on every failed check. It does not describe the shape of the result, but with no output schema that gap is modest given the failure-handling disclosure.

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?

Three sentences, front-loaded with the checklist, then the when-to-use condition, then the failure-behavior payoff. Nothing is repeated from the annotations and no sentence could be dropped without losing routing or behavioral information.

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 parameterless diagnostic tool this covers purpose, prerequisites, invocation timing, and what failures yield. The only shortfall is that it does not sketch what a successful result contains, though the absence of an output schema lowers that burden.

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?

The tool takes zero parameters at 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing because none exist.

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?

The description names a specific verb (check) and enumerates exactly what is verified: site reachability, pretty URLs, API enabled, Authorization header, Client ID, Redirect URI and scopes. That level of specificity makes it immediately distinguishable from diagnostic siblings such as get-system-info or get-account.

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?

It gives explicit triggers: when the user asks to check or troubleshoot the connection, or when other tools fail with connection or authorization errors. It also rules out a prerequisite by stating no sign-in is needed, so the agent knows it can be called before authenticating.

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

Deploy Server

Other Tools