Bizneo MCP Server and API by Cotlet

Get my timetable in Bizneo

bizneo_get_my_timetable

Read-onlyIdempotent

Get my timetable in the user's own Bizneo account from ChatGPT, Claude or any AI agent. Returns how to do it in Bizneo step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bizneo Cloud Browser. Bizneo's official API: Yes, Bizneo has a documented REST API, HCM API v1 (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": "bizneo_get_my_timetable"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful clarification that the tool 'opens nothing by itself' and returns screens, buttons, and fields instructions, making clear it is guidance rather than an action. It does not discuss permissions or staleness, but annotations cover the safety profile.

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 purpose and workflow are front-loaded, but 'from ChatGPT, Claude or any AI agent' is promotional filler and the official API sentence is a non-actionable aside that does not help invoke this tool. The result is adequate but not tight.

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 no-parameter guidance tool with rich annotations and no output schema, the description covers what is returned (step-by-step screens, buttons, fields), that no action occurs, and what to use next. It could mention prerequisites such as an open Cloud Browser session, but overall it is complete enough.

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 there is no parameter meaning to add; the baseline for a 0-param tool is 4. The description correctly does not invent parameters or suggest hidden inputs.

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 names the resource (timetable) and scope (the user's own Bizneo account), and clarifies that it returns step-by-step UI instructions rather than performing the action. It also distinguishes itself from the cotlet_browser_* tools that execute the steps. The opening phrase 'Get my timetable' could momentarily suggest data retrieval, keeping 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 Guidelines3/5

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

It gives a clear follow-on workflow: call this for steps, then use the cotlet_browser_* tools in the user's Bizneo Cloud Browser. However, it does not state when to prefer this over other Bizneo procedures or whether the official REST API is an alternative, so guidance is implied rather than explicit.

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

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