Skip to main content
Glama

Add a note to a prospect

addProspectNote

Add a note to one prospect (id from listProspects). Your whole team sees it on the prospect's page and in its activity log; the prospect never does.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "prospectId": "<prospectId>",
      "body": "<body>"
    },
    "name": "addProspectNote"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
prospectIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
bodyYes
authorYes
createdAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important visibility behavior: the whole team sees the note on the prospect page and activity log, while the prospect does not. It also discloses that Clera privately records inputs and results for usage tracking and support. It does not cover permissions or duplicate-handling behavior, but the added transparency is substantial.

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

Conciseness4/5

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

The description is short and front-loads the core action before explaining audience visibility and data recording. The privacy sentence earns its place because it discloses behavior not captured in the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, visibility, and the prospect-id source, and an output schema exists so return values need not be explained. However, it leaves the required note body underexplained and offers no guidance on alternatives or conditions, leaving gaps for a three-parameter mutation tool.

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

Parameters2/5

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

Schema description coverage is low at 33%, so the description should compensate. It adds useful meaning for prospectId by pointing to listProspects, but it says nothing about the required body parameter beyond the tool's name implying note text, and it does not clarify orgId beyond the schema's own description.

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?

The description states a specific verb and resource: 'Add a note to one prospect,' and narrows scope to a single prospect. It also points to listProspects as the source of the prospect id, making the action distinguishable for an agent.

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 description gives a prerequisite hint by saying the prospect id comes from listProspects, but it does not say when to use this tool versus alternatives or when not to use it. Usage is implied by the action itself rather than explicitly guided.

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