Skip to main content
Glama

Copy OneNote Page

copy_onenote_page

Copies a OneNote page to a destination section and starts the copy asynchronously in OneNote.

Instructions

Copy a OneNote page to another section. Runs asynchronously in OneNote.

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": {
      "page_id": "<page_id>",
      "section_id": "<section_id>"
    },
    "name": "copy_onenote_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage ID to copy
section_idYesDestination section ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive mutation; the description's most valuable addition is that the operation is asynchronous, warning the agent not to expect an immediate result. However, it does not say what the caller can do with the async result, whether the original page is left intact (implied by "copy" but not stated), or whether permission checks apply.

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 short sentences with zero filler, and the core action is front-loaded before the asynchronous caveat. Nothing could be removed without losing information.

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 two-parameter tool with full schema coverage and no output schema, the definition covers action and the key async caveat. The remaining gap is that with an async copy the description never tells the agent how or where the resulting page can be located, which matters for follow-up calls.

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 page_id and section_id both documented in the schema, so the baseline is 3. The description reinforces the source/destination mapping ("to another section") but adds no format, ID-shape, or validation detail beyond the schema.

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?

Specific verb and resource: "Copy a OneNote page to another section" names the operation, the source entity, and the destination scope. It does not distinguish itself from related page tools (e.g., how this differs from moving or duplicating behavior elsewhere in the catalog), so it stops short of a 5.

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

Usage Guidelines2/5

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

The description says what the tool does but gives no when-to-use guidance, no prerequisites (e.g., that the page_id must be an existing page in the source section), and no mention of alternatives or when a copy is preferred over manual recreation. "Runs asynchronously" is a behavioral note, not usage guidance.

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