Skip to main content
Glama
logisheets-mcp

logisheets-mcp

list_names

Read-only

Lists a workbook's defined names, including named ranges and constants, with sheet-qualified references for reuse in formulas.

Instructions

List the workbook's defined names (named ranges and named constants). Each has a name and what it refers to, sheet-qualified (e.g. "Sheet1!$B$2:$B$20" or "0.08"). A formula can use any of them as a reference: =SUM(Sales).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the bar for extra context is low. The description still adds real value beyond that: it states the shape of each entry (a name plus what it refers to) and pins down the reference format with sheet-qualified examples like "Sheet1!$B$2:$B$20" and the constant "0.08", which an agent cannot derive from the empty input schema.

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 short sentences, front-loaded with the purpose and followed by return-shape detail and a concrete formula example. The examples are load-bearing rather than decorative, though "Each has a name and what it refers to" slightly restates the preceding parenthetical and could be tightened.

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 zero-parameter, read-only listing tool with no output schema, the description supplies what the agent actually needs: what is enumerated, the format of the reference strings, and the fact that they are usable inside formulas. Only the absence of any cross-reference to sibling tools keeps it short of full completeness.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends its words on the return shape instead of inventing argument guidance.

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?

The description opens with a specific verb and resource — "List the workbook's defined names" — and immediately narrows scope with the parenthetical "(named ranges and named constants)", which rules out other kinds of name-like objects. It does not name or contrast with any sibling tool (e.g. list_blocks, chart_list), so differentiation relies on the resource being obviously distinct rather than on explicit routing.

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

Usage Guidelines3/5

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

Usage is only implied: the note that "A formula can use any of them as a reference: =SUM(Sales)" hints at the reason to call this (to learn what names exist before writing or evaluating formulas). There is no explicit when-to-use statement, no when-not to use it, and no pointer to alternatives such as get_cells for raw cell values.

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