Skip to main content
Glama
Sign In

Officient MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get calendar budget in Officient

officient_get_calendar_budget
Read-onlyIdempotent

Get calendar budget 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_get_calendar_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-open-world, but the description adds a genuinely important trait not captured there: the tool returns a textual walkthrough (screens, buttons, fields) and performs no actions itself. It does not detail length or format of that guide, so it falls short of 5.

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 resource, then the key caveat ('opens nothing by itself'), then the follow-up tool family. The opening clause about ChatGPT/Claude/AI agents and the closing API note are marketing flavor that could be trimmed, though the API note does justify the absence of an MCP server.

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 tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do, and which tools carry out the action. Only the guide's expected size or structure is left unspecified.

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 schema is an empty object with 100% coverage, so there are no parameters whose meaning needs explaining. Baseline of 4 applies; the description correctly implies no inputs are needed.

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 ('Get calendar budget in the user's Officient account') and immediately redefines the output: it returns step-by-step instructions rather than the data itself. That distinction lets an agent tell it apart from the cotlet_browser_* tools that actually perform the action.

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?

Explicitly routes the agent: this tool explains the procedure, then 'do it with the cotlet_browser_* tools in the user's Officient Cloud Browser.' It also states the tool 'opens nothing by itself,' clarifying the boundary. No exclusions or comparison against the other officient_* data tools, so not a full 5.

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 toolsInspect
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