Skip to main content
Glama

Coline

Show a sheet

show_sheet
Read-onlyIdempotent

Opens a sheet inside the chat as Coline's sheet editor, where the person can read it, switch views and edit cells. Use it when they want to see or work on a sheet.

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": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>"
    },
    "name": "show_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetIdYesSheet id from search, fetch or create_sheet.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
titleYes
sheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare this a non-destructive, idempotent, closed-world read, so the safety profile is covered. The description adds genuinely useful context — the tool opens an in-chat interactive editor where the human can switch views and edit cells — which explains why a readOnlyHint tool still enables editing by the person. It stops short of saying what is returned or what happens if the sheet or workspace is inaccessible.

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?

Two short sentences, front-loaded with what the tool does before the when-to-use clause. The second sentence largely restates the first ("see or work on a sheet" versus "read it... and edit cells"), so a small amount of redundancy keeps it below top marks.

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

Completeness3/5

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

Return values are covered by the output schema, parameters by a fully documented schema, and safety by annotations, so nothing essential is missing for calling it. The remaining gap is disambiguation from the read-oriented sheet siblings, which is the one thing only the description could supply and it does not.

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 coverage is 100% and both parameters document their own provenance ("from search, fetch or create_sheet", "from workspaces.list"), so the schema carries the load. The description contributes nothing about sheetId or workspace, which is acceptable at this coverage level but is the baseline rather than added value.

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?

"Opens a sheet inside the chat as Coline's sheet editor" gives a specific verb and resource and even characterizes the result as an interactive surface rather than raw data. That distinguishes it in spirit from read_sheet, but it never names the data-reading sibling, so the separation depends on the agent inferring that "read it, switch views and edit cells" means a UI rather than an API read.

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?

"Use it when they want to see or work on a sheet" is implied usage guidance only. With siblings like read_sheet and list_sheet_rows in the same catalog, an agent needs to know when to open the editor versus when to fetch row data programmatically, and no exclusion or alternative is stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources