note1

Export meeting

note1_export_meeting

Read-only

Export a meeting's summary and/or full speaker-attributed transcript as paste-ready markdown (or structured JSON). Use when the user wants the complete content, verbatim quotes, or a document to save.

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": {
      "meetingId": "<meetingId>"
    },
    "name": "note1_export_meeting"
  }
}

Input Schema

Name	Required	Description
`format`	No	Default: markdown
`teamId`	No	note1 team id; omit to use your active team
`content`	No	Default: both
`meetingId`	Yes	Meeting id (from search/list/calendar results)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 9, 2026

TDQS

A4.1/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 a closed world, so the safety profile is covered. The description adds behavior the annotations do not: the export is paste-ready markdown or structured JSON, and the transcript is speaker-attributed. It says nothing about payload size or pagination, which matters for a full-transcript export.

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?

Two sentences, both front-loaded: capability first, routing condition second. No filler, no restatement of the title or schema.

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?

For a 4-parameter read tool with no output schema, the description covers the two dimensions an agent would otherwise guess at (content scope and serialization format). The remaining unknowns, such as how the export is returned or how large it can get, are minor for this complexity level.

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 100% and defaults are already documented, so the baseline is 3. The description earns one step above that by clarifying what the 'transcript' content option actually yields ('full speaker-attributed') and what 'markdown' means in practice ('paste-ready'), which the enum labels alone do not 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 specific verb and resource ('Export a meeting's summary and/or full speaker-attributed transcript') plus the output form (markdown or JSON), which is clearly distinct from read-style siblings like note1_get_meeting or note1_get_meeting_notes. It never names those siblings, so the differentiation is inferred rather than explicit.

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 a clear selection condition: 'Use when the user wants the complete content, verbatim quotes, or a document to save.' That tells the agent when this beats a plain meeting fetch, but it states no when-not case and names no alternative tool explicitly.

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

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