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

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects Get Project Budget Item

projects_get_project_budget_item
Read-onlyIdempotent

Retrieve a specific budget item for a project or phase using project and budget item IDs to inspect budget details.

Instructions

Fetch a budget item under a project.

OpenAPI: GET /projects/{project_id}/budget_items/{budget_item_id} (getProjectBudgetItem).

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

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project or phase that owns the budget item.
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
Behavior2/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 contributes nothing beyond that—no note on error behavior for a missing item, cross-project access rules, or visibility/scoping caveats that an openWorld read would warrant.

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 padding. It is efficient, though the space saved is spent on an endpoint citation rather than on information that would actually help an agent choose the tool.

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?

An output schema exists, so return values need not be explained, and both required parameters are fully documented in the schema. What is missing for completeness is disambiguation from projects_get_budget_item, which matters given how many closely related siblings exist.

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%, and the parameter docs already explain that project_id may identify a project or a phase and that budget_item_id is the item ID. The description adds no extra meaning, so the baseline of 3 for a fully documented schema applies.

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: 'Fetch a budget item under a project', and pins it to the underlying operation (GET /projects/{project_id}/budget_items/{budget_item_id}). That separates it from the list-style sibling projects_list_project_budget_items, but the near-identical sibling projects_get_budget_item is never mentioned, so the agent must guess which getter applies.

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 when-to-use or when-not-to-use guidance at all. The OpenAPI path implies the tool needs both a project and a budget item ID, but nothing tells the agent how this differs from projects_get_budget_item or when the project-scoped variant is the correct choice.

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