Civitatis MCP Server and API by Cotlet

Update availability in Civitatis

civitatis_update_availability

Read-onlyIdempotent

Update availability in the user's own Civitatis account from ChatGPT, Claude or any AI agent. Returns how to do it in Civitatis step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Civitatis Cloud Browser. Civitatis's official API: Civitatis has no public API for suppliers (checked 11 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial context beyond the annotations: the tool opens nothing by itself, returns step-by-step instructions, and relies on the user's Civitatis Cloud Browser. It also discloses the checked absence of a public supplier API, which explains the workflow. This is rich behavioral disclosure for a read-only, non-destructive guide tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core information is front-loaded and useful, but the description includes marketing-style wording ('from ChatGPT, Claude or any AI agent') and a slightly redundant API note. It could be tightened without losing meaning.

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 zero-parameter, read-only guide tool with no output schema, the description covers what is returned, what the tool does not do, and how to proceed afterward. It is nearly complete, though it could be clearer about whether the returned steps are generic or specific to a particular availability change.

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 input parameters, so the baseline is 4. The description does not need to explain parameter semantics and correctly avoids inventing any.

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?

The description states the resource (Civitatis availability) and clarifies the actual operation: returning step-by-step instructions rather than performing the update. It distinguishes itself from the browser tools by naming cotlet_browser_* as the execution path. The leading phrase 'Update availability' is slightly misleading until corrected in the next sentence, which keeps it from a 5.

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

Usage Guidelines4/5

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

It clearly explains the usage pattern: call this tool to get step-by-step Civitatis screens/buttons/fields, then carry out the change with cotlet_browser_* tools in the user's Cloud Browser. It does not provide explicit when-not-to-use guidance, but the note about no public supplier API gives useful context for why this route is necessary.

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

All Civitatis MCP Server and API by Cotlet 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?