Signed

create_note

Add a note to a company, pitch, or person. The body is rendered as markdown, so headings, lists, and emphasis are formatted; plain text works too, with paragraphs and line breaks preserved. Give exactly one of company (a slug from list_companies / list_pitches) or person (a uuid from list_people). Set ai_generated: true when you (the AI) wrote the note yourself rather than transcribing the user's own words, so it can be visually distinguished from human-authored notes.

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

Input Schema

Name	Required	Description
`body`	Yes	The note text. Markdown is rendered.
`person`	No	Person to note, by uuid.
`company`	No	Company or pitch to note, by slug.
`ai_generated`	No	Set true if the note text is your own AI-written content, not the user's verbatim words. Defaults to false (attributed to the user as human-authored).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJul 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description adds real behavioral context beyond the schema: markdown rendering with paragraph/line-break preservation, the exactly-one-target constraint, and the semantic meaning of ai_generated for human-vs-AI attribution.

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?

Three tight sentences, front-loaded with the core action, then rendering behavior, then the identifier constraint and the ai_generated rule. Each sentence earns its place; the closing clause on visual distinction is slightly wordy but still informative.

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?

No output schema exists, so return values need not be described, and the description covers the target selection rule, body formatting, and the attribution flag. It leaves out edge-case behavior (e.g., supplying both company and person) and any permission/rate context, so it is complete but not exhaustive for a 4-parameter mutation tool.

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

Parameters4/5

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

Schema coverage is already 100%, so baseline is 3, but the description adds meaning the schema lacks: the one-of constraint on company vs person (the schema marks neither as required and has no oneOf), the slug-vs-uuid provenance, and the default/attribution intent of ai_generated. This meaningfully exceeds what the structured fields convey.

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?

States a concrete verb+resource ('Add a note') and names the three valid target entity types (company, pitch, person), which is more specific than most siblings. It does not explicitly contrast with sibling tools like create_transaction or update_company, so it stops short of full sibling differentiation.

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?

Gives clear operational context: exactly one of company/person must be supplied, and it points to the tools that yield valid identifiers (list_companies/list_pitches for slugs, list_people for uuids). It also says when to set ai_generated. No explicit when-not-to-use or alternative-tool routing, so it is clear context without full exclusion guidance.

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

All Signed tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?