losant-mcp-server: Skill for Claude Code

Add an MCP Tool Guide

Every losant_* tool has a companion guide resource served at losant://guides/tools/{toolName}. The tool's own description points at it ("Read losant://guides/tools/losant_x before using this tool"), so the guide — not the tool description — is where the procedure, parameter semantics, and resource-type tables live.

A guide is a JS module that builds one markdown string at module load from the maps in src/constants.js, then exports it. Tables are generated, never hand-written, so they cannot drift from the code.

1. Gather the facts first

Before writing anything, read:

• src/mcp/tools/<tool>.js — the real inputSchema, validation rules, and defaults. Every row of the Parameters table must match this file: which params are required, which are conditional and on what, which are rejected for which operations, what gets silently overwritten.
• src/constants.js — the resource lists and maps the tables are built from.
• An existing guide as the structural model: src/mcp/resources/tools/write-tool-guide.js (schema-driven columns) or delete-tool-guide.js (supported/unsupported column).

Do not describe behavior the tool does not have. If the guide would claim the tool errors on something, verify it in the tool source; document what actually happens, including silent coercions.

2. Create the file

Directory: src/mcp/resources/tools/

Filename: take toolName, strip the losant_ prefix, replace every _ with -, append -guide.js.

toolName	file
losant_query	query-tool-guide.js
losant_timeseries	timeseries-tool-guide.js
losant_device_state	device-state-tool-guide.js

Start from reference/guide-template.md in this skill directory and fill it in.

3. Section order

Every guide uses this order. Omit a section only if it genuinely does not apply; never reorder.

1. # Losant <Tool> Tool Guide — H1 title.
2. One or two sentences on what the tool is for and when to reach for it.
3. Any > warning blockquotes that must be read before anything else (destructive behavior, irreversibility, one-time secrets).
4. ## Before Calling — numbered prerequisite steps. If the tool needs an applicationId, step 1 links to the query guide rather than restating the procedure: Obtain \applicationId` by following the application-selection procedure in losant://guides/tools/losant_query.` Only the query guide spells that procedure out. Later steps walk the columns of the Resource Types table in the order the caller needs them.
5. ## Parameters — a table, then any > blockquotes for cross-parameter rules:

   | Parameter | Required | Description |
   |---|---|---|
   

   Required is Yes, No, or Conditional. A Conditional row must say what it is conditional on, pointing at a named column of the Resource Types table ("Required only for types that name a field in the parentResourceId column below"). Descriptions reference table columns in bold rather than duplicating their contents.
6. ## Resource Types — legend bullets, then the generated table, then the nested-type notes. One bullet per non-obvious column explaining what the value means and what — means in it. Columns are drawn from src/constants.js:
   • resource list — RESOURCE_TYPES, WRITABLE_RESOURCE_TYPES, or DELETABLE_RESOURCE_TYPES, whichever the tool accepts
   • NESTED_RESOURCES → parentResourceId column (`parentField` or —)
   • RESOURCE_TYPE_TO_GUIDE → Domain Guide column
   • RESOURCE_TYPE_TO_AUTHORING_GUIDE → Authoring Guide column (body-authoring tools only)
   • RESOURCE_TYPE_TO_QUERY_SCHEMA → Advanced Query Schema column (query-ish tools only)
   • NO_CREATE_TYPES → suppresses the Post schema link