Skip to main content
Glama

add_prospect_note

Add a timestamped note to a prospect's record (confirm-gated) — e.g. what was discussed on a call.

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": {
      "id": "<id>",
      "note": "<note>"
    },
    "name": "add_prospect_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

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?

Annotations establish this is a non-read-only but non-destructive write. The description adds two useful behavioral facts not in the annotations: notes are timestamped server-side, and the call is confirm-gated so a preview precedes execution. It doesn't say what the preview returns, but the confirm parameter's schema text covers that.

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?

A single front-loaded sentence with the key qualifier '(confirm-gated)' placed mid-sentence and an illustrative example at the end. No redundant wording, nothing that restates the schema.

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 a simple three-parameter write tool with no output schema, the definition covers purpose, the timestamping behavior, and the confirm gate; the confirm semantics are fully spelled out in the schema. Only the return shape (preview payload vs. created note) is left implicit.

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 only 33% (just 'confirm'), so id and note are undocumented structurally. The description implies id identifies a prospect record and note holds free-text content, partially compensating, but it never clarifies id format or note length/format expectations.

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 ('Add a timestamped note to a prospect's record') and adds a concrete example use case. It is unambiguous what the tool does, though it doesn't distinguish itself from other 'add_*' siblings beyond the resource name.

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?

The call-note example implies when to reach for this tool, and '(confirm-gated)' hints at a two-phase invocation. There is no explicit when-not guidance or comparison to alternatives such as update_prospect_status or add_checkin_log, so usage is only implied.

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.