Skip to main content
Glama
Sign In
mcp-server-smartsheet-rm

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects List Assignables

projects_list_assignables
Read-onlyIdempotent

Lists accessible projects and leave types with paginated results, helping you retrieve assignable items for scheduling and time tracking.

Instructions

List accessible assignables (projects and leave types).

OpenAPI: GET /assignables (getAssignables). Docs: https://developers.smartsheet.com/api/resource_management/openapi https://developers.smartsheet.com/_spec/api/resource_management/openapi.json

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

Input Schema

NameRequiredDescriptionDefault
pageNoResponse page to return, starting at 1 (default 1).
per_pageNoMaximum items per page, up to 1000 (default 20).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds one meaningful behavioral note — results are limited to what the caller can access — but says nothing about result volume, pagination defaults, or ordering beyond what the schema already encodes.

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?

The substantive content is a single front-loaded sentence that defines the resource, which is efficient. The OpenAPI path, operation id, and two documentation URLs are boilerplate metadata rather than guidance, though they are compact and do not bury the key sentence.

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 simple two-parameter read tool with a full output schema and comprehensive annotations, the description covers what the tool returns in domain terms (projects and leave types) and its access scoping. An agent has everything needed to call it; only cross-referencing with sibling endpoints is unaddressed.

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?

Both parameters (page, per_page) already have full descriptions in the schema, including defaults and the 1000 cap, so schema coverage is 100% and the baseline of 3 applies. The description adds no additional paging or filtering semantics beyond what is structured.

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?

States a specific verb and resource ("List accessible assignables") and immediately disambiguates the jargon by defining assignables as projects and leave types. That definition is genuinely useful. It does not, however, distinguish this tool from siblings like admin_list_leave_types or projects_list_projects, which surface overlapping data.

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: an agent can infer this is the endpoint for discovering which projects and leave types it may assign against. There is no explicit when-to-use, when-not-to-use, or named alternative for looking up projects or leave types through the dedicated list endpoints.

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