Skip to main content
Glama
Sign In

FieldEdge MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create work order in FieldEdge

fieldedge_create_work_order
Read-onlyIdempotent

Create work order in the user's own FieldEdge account from ChatGPT, Claude or any AI agent. Returns how to do it in FieldEdge step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's FieldEdge Cloud Browser. FieldEdge's official API: FieldEdge has an API, but only on request: customers ask for access through FieldEdge's onboarding form and get credentials for an app FieldEdge provisions (checked 8 Nov 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": "fieldedge_create_work_order"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with that while adding real context: nothing is opened or mutated, and execution requires a separate set of browser tools. The API-access caveat (credentials only via FieldEdge's onboarding form for a provisioned app) is useful operational context an agent could not infer from the schema.

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 behavior and the hand-off to browser tools are front-loaded and effective. However, the trailing API paragraph is long and tangential to calling this tool, and the parenthetical '(checked 8 Nov 2026)' is a stale verification stamp that does not help an agent act.

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, no-output-schema guidance tool, the description covers what it returns, what it does not do, and which sibling tools perform the actual work. The only real gap is that it never describes the shape or length of the returned instructions beyond 'screens, buttons, fields'.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description adds only scope framing (whose account, which agent), which is appropriate for a parameterless guidance tool.

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 a specific outcome: it returns step-by-step instructions for creating a work order in FieldEdge and explicitly does not perform the creation ('opens nothing by itself'). This disambiguates it from the cotlet_browser_* siblings that actually execute the steps, though the tool name's 'create' verb still implies a write that the tool never performs.

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 clear sequencing guidance: call this tool first for the procedure, then carry it out with the cotlet_browser_* tools in the user's FieldEdge Cloud Browser. It also covers the API-access alternative and its prerequisite (requesting credentials through FieldEdge onboarding). It does not state when this is not appropriate, so no explicit exclusions.

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

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