Skip to main content
Glama

HonestCRM

Add a note

add_note

Add a note to the timeline of a contact, company or deal.

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": {
      "target": "<target>",
      "body": "<body>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe note text.
targetYesThe record the note or call belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds the domain fact that the note is appended to a record's timeline rather than stored standalone, but says nothing about return value, whether the note is visible to others, or whether duplicates are possible.

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?

A single front-loaded sentence with no filler. It is efficient, though it is arguably too terse for a mutation tool given the guidance gaps elsewhere.

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?

With only two fully documented parameters via a nested schema and no output schema, the description covers the minimum an agent needs to invoke it. It does not address side effects such as notifications, ordering in the timeline, or editability of the note, which would round out a write tool with no output schema.

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%: both `body` and the nested `target.type`/`target.id` are documented in the schema, including the UUID pattern and the hint to use search for the id. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

"Add a note" states a specific verb and resource, and the description pins down where the note lands: the timeline of a contact, company or deal. This is unambiguous for an agent, though it does not contrast itself with siblings such as log_call or create_task.

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

Usage Guidelines2/5

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

The description says what the tool does but never when to reach for it versus an alternative. There is no mention of log_call (which the schema hints at by calling the parent "the record the note or call belongs to") or of create_task for actionable items.

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