Clarifo

notes

Read-onlyIdempotent

The user's own Clarifo notes, newest first: what they wrote down in Clarifo or asked an assistant to remember. Use it before continuing a note and to find a note to work into a document. When the user asks what they noted about a company, show the notes with open_in_clarifo(notes_company=...) (one note: note_id) and say in a sentence or two what they say; give note_url only when the user wants to open the note on clarifo.com. Read-only.

Args: note_id: One note in full (text, companies, documents made from it). company: Only notes tagged with this company (name or ticker). query: Only notes whose title or text contains these words. limit: Up to 50 (default 20).

Returns: {"notes": [{"note_id", "title", "preview", "companies", "updated_at", "editable", "note_url"}], "total"} or {"note_id", "title", "text", "companies", "documents", ...}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`company`	No
`note_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered; the description reinforces read-only and adds the newest-first ordering plus the limit cap. It does not discuss pagination or total/limit interaction, which would be the remaining useful behavioral detail.

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?

Front-loaded with purpose and the key routing rule before the Args/Returns blocks. The Returns section largely restates what the output schema already provides, which is wasted space, but the rest is dense and earns its place.

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

Completeness5/5

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

For a four-parameter read tool with an output schema, the description covers purpose, usage routing, all parameters, ordering, and limits. An agent could select and invoke this correctly without opening the schema.

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 0%, so the description carries the full burden and mostly meets it: note_id means one note in full, company accepts name or ticker, query matches title or text words, limit is capped at 50 with default 20. It does not state whether these filters combine or whether note_id overrides the others, which is the one meaningful gap.

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 names a specific resource (the user's own Clarifo notes), states ordering (newest first), and covers both modes (list notes vs. one full note by note_id). It also distinguishes itself from open_in_clarifo, which is the tool to use for surfacing notes to the user.

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?

It gives explicit when-to-use triggers ('before continuing a note', 'to find a note to work into a document') and an explicit alternative for the related case (show notes via open_in_clarifo(notes_company=...)) with a note about when to include note_url. Nothing is left to inference.

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

All Clarifo 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.