Skip to main content
Glama
Sign In

Ordrestyring MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Plan an employee in Ordrestyring

ordrestyring_plan_an_employee
Read-onlyIdempotent

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

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?

Beyond the readOnly/idempotent/destructive annotations, it discloses the actual return content (screens, buttons, fields) and explicitly states it 'opens nothing by itself' — a meaningful behavioral guarantee that prevents an agent from assuming the action is executed. It does not mention prerequisites such as an active browser session or login state, which would complete the picture.

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?

The operative content — what it returns and that it does not act — is front-loaded in the first sentence. The trailing sentence about the GraphQL API and the absence of an official MCP server is somewhat tangential metadata, and the parenthetical '(checked 31 Oct 2026)' is noise that does not help invocation.

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 planning tool with no output schema, the description covers purpose, return content, and the follow-up execution path. It stops short of describing the shape of the returned plan or any session prerequisites, but nothing essential for a correct call is missing.

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 tool takes zero parameters, so the baseline is 4. There is nothing parameter-related for the description to compensate for, and the schema coverage signal is 100%.

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 ('Plan an employee in the user's own Ordrestyring account') and immediately disambiguates the ambiguous verb 'plan' by saying it returns step-by-step instructions rather than performing the action. An agent can distinguish this from the cotlet_browser_* execution tools without opening any schema.

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?

Gives clear usage context and routes the agent onward: get the plan here, then execute it with the cotlet_browser_* tools in the user's Ordrestyring Cloud Browser. It lacks an explicit 'do not use this when...' exclusion, so it stops short of the top band.

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

All Ordrestyring 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