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

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects Get Assignable

projects_get_assignable
Read-onlyIdempotent

Fetches one assignable by ID (project or leave type) to retrieve its details for scheduling, time tracking, and resource management.

Instructions

Fetch one assignable by ID (project or leave type).

OpenAPI: GET /assignables/{assignable_id} (getAssignablesId).

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": {
      "assignable_id": "<assignable_id>"
    },
    "name": "projects_get_assignable"
  }
}

Input Schema

NameRequiredDescriptionDefault
assignable_idYesID of the project or leave type.

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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — that the ID may resolve to either a project or a leave type — plus an OpenAPI operation mapping, but says nothing about auth, error cases, or response shape.

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 the purpose; nothing is padded. The OpenAPI line is arguably developer-facing noise but is compact and placed last, so it does not obstruct scanning.

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 single-parameter read with a documented schema, full annotations, and an output schema that covers return values, the description supplies everything needed to invoke it correctly. The only shortfall is the absence of routing guidance among the many sibling getters.

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 the single parameter is already documented as "ID of the project or leave type." The description restates the same polymorphism rather than adding format, example, or resolution semantics, so the schema does the heavy lifting.

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 gives a specific verb and resource ("Fetch one assignable by ID") and disambiguates what an assignable is — either a project or a leave type. It clearly contrasts with a list operation by saying "one," though it never names projects_list_assignables or projects_get_assignment explicitly.

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 implied: call this when you already hold an assignable ID and need the single record. There is no explicit when-to-use versus projects_list_assignables or projects_get_assignment, and no stated prerequisites or failure conditions (e.g., unknown ID behavior).

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