Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_get_folder_metadata

Retrieve metadata like name and parent info for a folder using its ID, enabling quick access to folder properties without loading sheets.

Instructions

Lightweight metadata for a folder.

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": {
      "folder_id": "<folder_id>"
    },
    "name": "smartsheet_get_folder_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations provided. Description doesn't disclose whether it's read-only, destructive, or any behavioral traits. 'Lightweight metadata' implies a safe read operation, but it's not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 5 words, but this is under-specification rather than helpful conciseness. The single sentence is vague and doesn't earn its place.

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

Completeness1/5

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

Given the tool's simplicity (1 param, no output schema, no annotations), the description is completely inadequate. It doesn't explain the response or differentiate from siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description adds no meaning to the folder_id parameter beyond the schema. No format, constraints, or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Lightweight metadata for a folder.' This indicates a get operation on folder metadata, but doesn't clarify what 'lightweight' includes versus sibling tools like smartsheet_get_folder. It's better than tautology but lacks specificity to distinguish.

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

Usage Guidelines1/5

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

No guidance on when to use this tool vs alternatives like smartsheet_get_folder or smartsheet_list_folder_children. No context provided.

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