Skip to main content
Glama

SalesHookAI

Add measurement

addProjectMeasurement

Saves a measurement or site-survey entry (Aufmaß: dimensions, areas, quantities) to a project. With source "photo" (values read from a photo, not given by the user) the entry is saved as an unconfirmed draft (status pending) that the user has to verify before it is used for billing.

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": {
      "title": "<title>"
    },
    "name": "addProjectMeasurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAdditional notes
unitNoUnit like m2, m, lm, stk
titleYesShort label for the measurement, e.g. "Wohnzimmerboden"
valueNoCalculated numeric value, e.g. 21.32
sourceNo"photo" if these values were estimated from an attached image rather than stated by the user; omit for manual dictation
fileIdsNoIDs of project files (photos) this measurement was derived from, e.g. from a prior addProjectFileFromChat call
formulaNoFormula used, e.g. "5.20 * 4.10"
projectIdNoNumeric ID of the project
dimensionsNoObject with dimensions, e.g. {"length": 5.2, "width": 4.1}
surveyDateNoDate of the survey (YYYY-MM-DD)
projectNameNoName of the project (used if projectId is not given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses a non-obvious behavioral trait: photo-derived entries are saved with status pending and are excluded from billing until verified. It does not state the status/effect of the non-photo path or what happens on duplicate calls, which matters given idempotentHint=false.

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, and the core action is front-loaded before the conditional caveat. Nothing could be removed without losing information.

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 an 11-parameter mutation tool with a nested dimensions object and no output schema, the description covers the one genuinely surprising behavior (pending draft on photo source). It omits what the call returns (e.g. the created measurement ID) and does not clarify projectId vs projectName resolution beyond what the schema states.

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 description coverage is 100%, so the schema already documents all 11 parameters, including the source and fileIds semantics. The description's mention of source="photo" largely restates the schema's own description of that field, adding the draft/pending consequence rather than new per-parameter meaning.

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 uses a specific verb and resource ("Saves a measurement or site-survey entry") and grounds it in domain terms (Aufmaß: dimensions, areas, quantities). It is clearly a write counterpart to the fetch-style sibling getProjectMeasurements, though it does not name that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one conditional usage rule: when source is "photo", the entry is stored as a draft the user must verify. There is no guidance on when to choose this tool over alternatives (e.g. addBoardNotes) or prerequisites such as needing an existing project, so usage is only partially covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources