Skip to main content
Glama
Sign In
camcors-mcp

camcors-mcp

by Davidobot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save report edits

camcors_save_report_edit

Save a previously previewed report edit after the user explicitly confirms the save.

Instructions

Save a previously previewed report edit. Call only after the user has reviewed the visible CamCORS form and explicitly confirmed the save.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "previewToken": "<previewToken>",
      "confirm": "<confirm>"
    },
    "name": "camcors_save_report_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true after explicit user confirmation
previewTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations show readOnlyHint=false (write) and destructiveHint=false. Description adds save-after-preview context but does not disclose potential side effects or persistence details. No contradiction with annotations.

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?

Two sentences with no filler. Front-loaded action and immediate precondition. Every sentence adds value.

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?

Given 2 required parameters and no output schema, description covers purpose and precondition well. Could mention post-save behavior (e.g., confirmation message) but not essential.

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 50%. Description echoes schema for 'confirm' (must be true after confirmation). PreviewToken is not elaborated beyond schema's pattern/format. Baseline 3 is appropriate.

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?

Description clearly states verb and resource: 'save a previously previewed report edit'. It distinguishes from siblings like camcors_prepare_report_edit (preview) and camcors_discard_report_preview (discard).

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?

Provides explicit precondition: 'Call only after the user has reviewed the visible CamCORS form and explicitly confirmed the save.' Does not name alternatives but context from siblings implies when not to use.

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

Deploy Server

Other Tools