Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_get_sent_update_request

Retrieve details of a specific sent update request by providing the sheet ID and sent update request ID.

Instructions

Get a single sent update request.

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": {
      "sheet_id": "<sheet_id>",
      "sent_update_request_id": "<sent_update_request_id>"
    },
    "name": "smartsheet_get_sent_update_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheet_idYesSmartsheet sheet ID.
sent_update_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states 'Get,' implying a read-only operation, but does not mention any side effects, authentication requirements, or what happens if the request is not found. This is insufficient for a mutation-free tool.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks necessary detail. It meets the minimum for brevity but sacrifices completeness.

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?

Given the low complexity (2 required parameters, no output schema), the description provides the basic purpose. However, it omits important details like the return structure or confirmation of success, making it minimally adequate.

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

Parameters2/5

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

Schema description coverage is 50%: only sheet_id has a description. The tool description adds no additional meaning beyond the schema. It does not explain what the sent update request ID represents or how to obtain it, leaving the agent with incomplete parameter understanding.

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 clearly states the tool retrieves a single sent update request. However, it does not distinguish from sibling tools like smartsheet_get_update_request or smartsheet_list_sent_update_requests, which have overlapping functionality.

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?

No guidance on when to use this tool versus alternatives. The description lacks any context about prerequisites, such as needing the sheet ID or sent update request ID, or when to prefer this over list or other get tools.

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