Officient MCP Server and API by Cotlet

List documents in Officient

officient_list_documents

Read-onlyIdempotent

List documents in the user's own Officient account from ChatGPT, Claude or any AI agent. Returns how to do it in Officient step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Officient Cloud Browser. Officient's official API: Officient has an API but no official MCP server (checked 22 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": "officient_list_documents"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With readOnlyHint=true already declared, the description usefully adds that it 'opens nothing by itself' and only returns instructions, which tells the agent it must take a follow-up action to accomplish anything. The API/MCP-server status note adds context about scope, though it is dated trivia rather than behavior.

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 instruction is front-loaded, but 'from ChatGPT, Claude or any AI agent' and the dated API survey sentence ('checked 22 Oct 2026') are filler that does not help an agent decide or call correctly. It is one long run-on with the key facts buried mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of explaining what comes back; it does say a step-by-step guide is returned, but not its shape or how to consume it. For a zero-parameter instruction tool this is adequate but thin.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline applies. No misleading parameter claims are made.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does clarify that the tool returns a step-by-step how-to rather than the documents themselves, which is valuable. But 'List documents in the user's own Officient account' promises a data listing that the tool does not perform, so name and description pull in different directions. It also repeats the separate cotlet_browser_* workflow without distinguishing why this tool exists alongside cotlet_app_guide.

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 gives a clear two-step usage pattern: call this for instructions, then perform the actions with cotlet_browser_* tools in the Officient Cloud Browser. It does not name when to prefer cotlet_app_guide over this, but the sequencing guidance is explicit and usable.

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

All Officient 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?