Skip to main content
Glama
Sign In
jobber-mcp

jobber-mcp

by sanjibani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_client_note

Add a note to a client record to document interactions like phone calls or site visits. Specify the client, note content, and optionally pin the note for visibility.

Instructions

Add a note to a client's record. Useful after a phone call or site visit.

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": {
      "client_id": "<client_id>",
      "body": "<body>"
    },
    "name": "add_client_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pinnedNo
client_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Add a note,' implying mutation, but does not explain whether notes are appended, overwritten, or if special permissions are needed.

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?

The description is two sentences long with no unnecessary words, efficiently conveying the core purpose.

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

Completeness2/5

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

Despite having an output schema, the description is too minimal. It fails to explain the effect on the client record, the structure of the note, or any important details about parameters and return values.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the description adds no information about the three parameters (body, pinned, client_id). The description does not compensate for the lack of documentation in the schema.

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 clearly states 'Add a note to a client's record' with a specific verb and resource. It distinguishes itself from sibling tools like create_client and list_clients, which serve different purposes.

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?

The description suggests usage 'after a phone call or site visit,' providing some contextual guidance. However, it does not explicitly state when not to use or mention any alternatives.

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