Skip to main content
Glama

NoMac

by app.nomac
OverviewDiscussionsAdmin

Report an issue to NoMac support

report_issue

Sends NoMac support an error the tools could not resolve, with the Mac (session_id, job_id) or build (ref_id) it is about; repeats are merged, and email asks for a direct reply. kind feedback sends a note instead. Without description, returns support's replies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoproblem (default): an error for support to answer. feedback: a note on what got in the way or was missing; it needs no answer. Leave out code, secrets and personal data.
emailNoOptional address for a direct reply from NoMac support. Only when the user asks for one.
job_idNoCommand job ID (job_…) the issue is about.
ref_idNoBuild ID or other NoMac reference the issue is about.
session_idNoMac session ID (ses_…) the issue is about.
descriptionNoWhat went wrong, including the tool, arguments and error you saw. Omit it to read replies to earlier reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / email / format
      Removed value: -"email"
    • removedInput schema / properties / email / pattern
      Removed value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedInput schema / properties / kind / description
      Previous value: -"problem (default): an error the tools could not resolve, for support to answer. feedback: a note for NoMac about what got in the way, failed, was missing from the Mac or the tools, or would have saved time; it needs no answer. Leave out code, secrets and personal data."New value: +"problem (default): an error for support to answer. feedback: a note on what got in the way or was missing; it needs no answer. Leave out code, secrets and personal data."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": {},
-  "description": "The JSON response of the NoMac API for this operation",
-  "properties": {
-    "error": {
-      "additionalProperties": {},
-      "description": "Present only when the call failed",
-      "properties": {
-        "code": {
-          "description": "Stable machine-readable error code, for example insufficient_credit",
-          "type": "string"
-        },
-        "message": {
-          "description": "What went wrong and what to do next",
-          "type": "string"
-        }
-      },
-      "required": [
-        "code",
-        "message"
-      ],
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "problem (default): an error the tools could not resolve, for support to answer. feedback: a note for NoMac about what got in the way, failed, was missing from the Mac or the tools, or would have saved time; it needs no answer. Leave out code, secrets and personal data.",
+  "enum": [
+    "problem",
+    "feedback"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that repeats are merged, that supplying email requests a direct reply from support, and that omitting the description turns the same tool into a read of support's replies — an important non-obvious dual behaviour for a tool flagged readOnlyHint=false. It does not say whether reports are visible to other users or what happens after submission, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences front-load the action and pack in the dedup rule, email semantics, feedback variant and read mode with no filler. The compressed semicolon style is dense but every clause carries a distinct fact.

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?

With no output schema, the description correctly covers the return behaviour (support's replies when called without a description). The only gap is that with zero required parameters it never states the minimum viable call — e.g. whether at least one of description or an identifier is needed to file versus read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is already documented in the schema; the description mainly restates the Mac-vs-build split for session_id/job_id versus ref_id. It adds the useful framing that these identify what the issue is about, but no format or mutual-exclusion guidance beyond the schema. Baseline 3 applies.

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 (sends NoMac support an error) plus the payload it carries (session_id/job_id for a Mac, ref_id for a build), so the agent knows exactly what the call does. No sibling tool overlaps this purpose, and the feedback variant and read-replies mode are distinguished inline.

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?

"An error the tools could not resolve" gives a clear trigger condition, and "kind feedback sends a note instead" routes the alternative case. What is missing is an explicit when-not (e.g. don't file reports for ordinary user input mistakes) and whether identifiers are truly optional.

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

All NoMac toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources