mcp-creatio

Get the current Creatio user

get-current-user-info

Read-only

Retrieves the current Creatio user’s identity, roles, and local time info so you can set correct record owners and author IDs and calculate dates like today or overdue.

Instructions

Returns the Creatio user this server acts as: { success, userInfo: { id, contactId, contactName, email, cultureInfo, timeZone, utcOffset, now, today, userRoles, ... } }. Call it once before creating records owned by the user — owner/author lookups (OwnerId, AuthorId) take userInfo.contactId, not userInfo.id — or when a tool needs the user as a user/role (adminUnitId = userInfo.id). Also call it once when dates matter: now / today are the user's current date and time, the base for tomorrow, this month or overdue. Reuse the result for the rest of the conversation. timeZone (IANA, e.g. "Europe/Kyiv") and utcOffset (today's, e.g. "+02:00") are the user's Creatio time zone — the one record dates are read and written in (get-guide: datetime-guide). See get-guide: contactid-guide.

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": "get-current-user-info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.5Jun 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark it read-only and closed-world, so the bar is lower, yet the description adds substantial non-obvious behavior: which ID field to use for OwnerId/AuthorId versus adminUnitId, that now/today are the user's current date and time, and that timeZone is the zone record dates are read and written in. It also names the guides that carry deeper semantics.

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 return shape and then the call conditions, and every clause carries information. It is a single dense paragraph with nested parentheticals, which makes it slightly harder to scan than it needs to be.

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?

With no output schema and no parameters, the description carries the full burden and meets it: it enumerates the returned fields, explains the ID distinction, defines the time-zone fields, and gives caching guidance. An agent has everything needed to call it correctly and interpret the result.

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?

There are zero parameters, so the baseline is 4. The description instead spends its parameter budget documenting the response fields (id, contactId, timeZone, utcOffset, now, today), which is useful but is not input semantics.

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 ('Returns the Creatio user this server acts as') and immediately lists the exact response shape, so there is no ambiguity about what comes back. No sibling tool does anything similar, and the description makes that distinct identity obvious.

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 explicit triggers: call once before creating records owned by the user, when a tool needs the user as a user/role, or when dates matter. It also tells the agent to reuse the result for the rest of the conversation, which is a concrete when-not-to-call-again rule.

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