Skip to main content
Glama
Sign In
OriginLab-MCP

OriginLab-MCP

by Yike-Ye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

origin_worksheet_info

Retrieve worksheet details—size, column names, and formats—instantly without loading data. Specify a book and sheet, or omit both to target the active sheet, enabling quick structural overviews.

Instructions

Describe a worksheet -- size, column names, formats -- without reading it.

Omit both arguments for the active worksheet.

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": "origin_worksheet_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNo
sheetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. It usefully discloses that the tool does not read worksheet contents and returns descriptive metadata only. It stops short of stating behavior on missing worksheets or confirming the absence of side effects.

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 with no filler; the core purpose is front-loaded and the active-worksheet note is placed second. Every clause 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?

The output schema covers return structure, so the description need not explain it. With only two optional parameters, the active-worksheet behavior is stated, and the metadata scope is explicit, making the definition complete for this simple 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?

The schema has no parameter descriptions, but the description adds key semantics: omitting both arguments targets the active worksheet. The titles 'Book' and 'Sheet' plus the tool's context make the remaining mapping reasonably clear.

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 states a clear verb and resource: 'Describe a worksheet' with concrete metadata delivered (size, column names, formats). The qualifier 'without reading it' distinguishes it from the sibling origin_worksheet_read, making its purpose unambiguous.

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?

It gives a practical invocation rule: omit both arguments to target the active worksheet. It doesn't explicitly name alternatives or when-not-to-use conditions, but the 'without reading it' contrast implies the read sibling would be used when cell data is needed.

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