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

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects List Project Budget Items

projects_list_project_budget_items
Read-onlyIdempotent

List budget items for a project or phase by type (TimeFees, TimeFeesDays, or Expenses) to review and manage financial data.

Instructions

List project/phase budget items of the given type.

OpenAPI: GET /projects/{project_id}/budget_items (getProjectBudgetItems). item_type is required (BudgetItemType: TimeFees, TimeFeesDays, or Expenses).

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": {
      "project_id": "<project_id>",
      "item_type": "<item_type>"
    },
    "name": "projects_list_project_budget_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_typeYesBudget item type: TimeFees, TimeFeesDays or Expenses.
project_idYesID of the project or phase.

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the underlying endpoint mapping but says nothing about pagination, result ordering, or empty-result behavior that a listing tool would benefit from.

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?

Three short lines with the core purpose front-loaded and no filler. The OpenAPI endpoint line is developer-facing metadata that adds modest value rather than padding.

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 two-parameter read-only list tool with full schema coverage, complete annotations, and an output schema, the description covers what is needed to call it correctly. Only the absence of guidance relative to the singular 'get' sibling leaves a small gap.

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 description coverage is 100%, so both parameters are already documented in the schema. The description repeats the item_type enum values and the requirement constraint without adding meaning such as filtering behavior or accepted ID forms for project_id (which the schema allows as integer or string).

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 states a specific verb and resource: 'List project/phase budget items of the given type', which scopes the collection being returned. It implicitly contrasts with the singular sibling 'projects_get_project_budget_item', but never names an alternative 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 only implied by the verb 'List' plus the note that item_type is required. There is no explicit statement of when to prefer this over projects_get_project_budget_item or how to choose between the three budget item types beyond restating the enum.

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