Skip to main content
Glama

createNote

Add a note to a contact by specifying their ID and note content. Simplify communication tracking and information management within Clay's unified platform.

Instructions

Create a note for a contact. Only use this when the user explicitly asks to create, add, or save a note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_idYesThe ID of the contact to add the note to.
contentYesThe content of the note.

Implementation Reference

  • index.js:240-251 (registration)
    Registration of the 'createNote' MCP tool, including name, description, Zod input schema, and inline execute handler that proxies requests to the external Clay API endpoint '/note' via the callTool helper.
    server.addTool({
      name: "createNote",
      description:
        "Create a note for a contact. Only use this when the user explicitly asks to create, add, or save a note.",
      parameters: z.object({
        contact_id: z
          .number()
          .describe("The ID of the contact to add the note to."),
        content: z.string().describe("The content of the note."),
      }),
      execute: async (params, { session }) => callTool("/note", params, session),
    });
  • Zod schema defining input parameters: contact_id (required number) and content (required string).
    parameters: z.object({
      contact_id: z
        .number()
        .describe("The ID of the contact to add the note to."),
      content: z.string().describe("The content of the note."),
    }),
  • The execute handler for the tool, which calls the shared callTool utility to POST the parameters to 'https://nexum.clay.earth/tools/note' with API key authentication.
    execute: async (params, { session }) => callTool("/note", params, session),
  • Shared helper function used by multiple tools (including createNote) to proxy requests to the backend Clay API service.
    async function callTool(path, params, session) {
      console.log('Calling tool', path, session)
      return fetch(`https://nexum.clay.earth/tools${path}`, {
        body: JSON.stringify(params),
        headers: {
          Authorization: `ApiKey ${session.apiKey}`,
          "Content-Type": "application/json",
        },
        method: "POST",
      }).then((res) => res.text());
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it implies a write operation ('Create'), it doesn't address permissions, error handling, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise with two sentences that each serve a clear purpose: stating the tool's function and providing usage guidelines. There's no wasted language, and it's effectively front-loaded.

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?

Given the tool's complexity (a simple creation operation with 2 parameters), 100% schema coverage, and no output schema, the description is minimally adequate. It covers purpose and usage but lacks behavioral details that would be helpful for a mutation tool without annotations.

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%, with both parameters ('contact_id' and 'content') fully documented in the schema. The description doesn't add any additional meaning or context beyond what the schema provides, so it meets the baseline score for high schema coverage.

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 clearly states the action ('Create a note') and target resource ('for a contact'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'getNotes' or 'searchInteractions' beyond the creation aspect, which prevents a perfect score.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Only use this when the user explicitly asks to create, add, or save a note.' This clearly defines when to invoke the tool versus alternatives, offering strong operational constraints.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clay-inc/clay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server