Skip to main content
Glama
CRACKISH

mcp-creatio

by CRACKISH

Call a Creatio configuration REST service method

call-configuration-service

Invoke any Creatio configuration REST service directly. Use when no dedicated MCP tool covers the operation. Specify service name, method, and optional body or query parameters.

Instructions

Escape hatch for invoking any configuration-package REST service exposed at /0/rest//. Use this when no dedicated MCP tool covers the operation. Always prefer the specific tools (upsert-admin-operation, refresh-feature-cache, sys-settings tools, etc.) when they exist — they validate inputs, handle wrapped responses, and document side effects. Returns {status, contentType, body}; JSON responses are auto-parsed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body sent as JSON for POST/PATCH/PUT. Ignored for GET/DELETE. Pass the service parameters as a flat object (e.g., {"recordId":"<guid>","name":"..."}). Creatio configuration services use [WebInvoke BodyStyle=Wrapped], so each parameter becomes a top-level key.
queryNoOptional query-string parameters appended to the URL.
methodYesService method name (UriTemplate) to invoke (e.g., "UpsertAdminOperation").
serviceYesConfiguration service name as registered in Creatio (e.g., "RightsService"). The full URL is /0/rest/<service>/<method>.
httpMethodNoHTTP method. Most Creatio configuration services use POST.POST
Behavior4/5

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

No annotations exist, so the description carries full burden. It states the return format and auto-parsing behavior, and implies that this tool lacks input validation and response handling compared to dedicated tools. However, it does not mention potential side effects, destructive actions, or rate limits, which would enhance transparency.

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 that are perfectly front-loaded with purpose, each earning its place. No redundant phrases or unnecessary detail. Highly efficient.

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?

Given no output schema, description fully covers return values (`{status, contentType, body}`) and auto-parsing. All five parameters are described adequately, and the escape-hatch nature is fully contextualized with sibling tool references.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema: explains that `body` is ignored for GET/DELETE, describes the wrapped request format, details URL construction, and clarifies defaults. This provides agents with practical usage context.

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?

Description clearly states it is an 'escape hatch for invoking any configuration-package REST service' and gives the URL pattern. It distinguishes itself by listing dedicated tools to prefer, making the purpose specific and unambiguous.

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 tells when to use ('when no dedicated MCP tool covers the operation') and when not to ('Always prefer the specific tools'). Provides concrete examples of sibling tools, offering clear guidance on alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CRACKISH/mcp-creatio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server