Skip to main content
Glama
Sign In

FieldEdge MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Dispatch technician in FieldEdge

fieldedge_dispatch_technician
Read-onlyIdempotent

Dispatch technician 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_dispatch_technician"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds important behavioral context: it returns procedural guidance and 'opens nothing by itself.' It also notes FieldEdge API access constraints, helping the agent understand this is a guide, not an executor.

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 description is front-loaded with the core behavior and next-step guidance. The final API-access detail is useful context but somewhat tangential, and the parenthetical date adds minor length without changing usage.

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

Completeness5/5

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

For a zero-parameter instructional tool with no output schema, the description supplies what an agent needs: the return format (screens, buttons, fields), the fact that it performs no action, and the browser tools to use afterward. Nothing essential 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 has zero parameters, so there are no parameter semantics to clarify. The baseline for a parameterless tool is 4, and the description does not need to compensate for missing schema coverage.

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?

The description states a specific purpose: it returns step-by-step instructions for dispatching a technician in FieldEdge, rather than performing the dispatch itself. It explicitly clarifies that it opens nothing by itself and directs execution to the cotlet_browser_* tools, distinguishing it from those siblings.

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?

The description clearly tells the agent to use this tool to get FieldEdge screens/buttons/fields, then use the cotlet_browser_* tools to carry out the action. It does not explicitly name when to avoid this tool versus cotlet_app_guide or other alternatives, but the intended workflow is clear.

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