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

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects Get Budget Item

projects_get_budget_item
Read-onlyIdempotent

Fetch a specific budget item by ID from Smartsheet Resource Management to review project budget and cost details.

Instructions

Fetch a budget item by ID.

OpenAPI: GET /budget_items/{budget_item_id} (getBudgetItem).

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": {
      "budget_item_id": "<budget_item_id>"
    },
    "name": "projects_get_budget_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_item_idYesID of the budget item.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

C2.9/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. The description adds only the underlying OpenAPI operation (GET /budget_items/{budget_item_id}), which is mildly useful for understanding the remote call but discloses nothing about errors, permissions, or missing-ID behavior beyond the annotations.

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 lines with the action front-loaded and no filler. The OpenAPI line is slightly redundant given the tool name but is cheap and helps map to the REST surface.

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?

For a single-parameter read with annotations and an output schema, the description is functionally sufficient. What it omits is the sibling disambiguation an agent needs to choose this over projects_get_project_budget_item, which is the one gap that matters here.

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% for the single budget_item_id parameter, so the schema already explains the ID. The description adds no format, type tolerance (integer or string per the anyOf), or example that would extend meaning; the baseline of 3 is appropriate.

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?

States a specific verb and resource ("Fetch a budget item by ID") and echoes the endpoint, so the basic action is legible. However, among siblings such as projects_get_project_budget_item and projects_list_project_budget_items it never clarifies whether this returns a project-scoped budget item or a different budget-item entity, leaving real ambiguity about what resource is being fetched.

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?

There is no guidance on when to use this tool versus the near-named sibling projects_get_project_budget_item, and no exclusions or prerequisites. The agent must infer selection purely from names, which the definition does nothing to disambiguate.

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