Skip to main content
Glama

Operations Parts Tool

operations-parts
Read-only

Reads bounded parts stock, technician exposure, and transaction metadata for the authenticated workspace without exposing amounts, item pricing, or private notes. Use to inspect parts and inventory exposure in the connected business. Returns inventory, transactions, technician_exposure, summary, filters, scope.

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": "operations-parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum inventory, transactions, and technician balances to return.
technician_idNoOptional same-business technician ID.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
filtersYesFilters metadata; empty collections retain their existing JSON array representation.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.
inventoryYesBounded inventory records returned by this tool.
transactionsYesBounded transactions records returned by this tool.
technician_exposureYesBounded technician exposure records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "filters": {
      +      "description": "Filters metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "inventory": {
      +      "description": "Bounded inventory records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "technician_exposure": {
      +      "description": "Bounded technician exposure records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "transactions": {
      +      "description": "Bounded transactions records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "inventory",
      +    "transactions",
      +    "technician_exposure",
      +    "summary",
      +    "filters",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the description does not need to restate safety. It adds real value by disclosing what is deliberately withheld (amounts, item pricing, private notes) and that results are bounded, which shapes how an agent should interpret and trust the output.

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 sentences, front-loaded with the resource and the privacy constraint. The final sentence enumerating return keys (inventory, transactions, technician_exposure, summary, filters, scope) is largely redundant given the output schema and is the one place that does not earn its space.

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?

With annotations covering the safety profile and a full output schema, the description only needs to frame intent and constraints. It does that, including the privacy exclusions, though it could have said a word about how limit interacts with the listed payload sections.

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 both parameters (limit, technician_id) are fully documented in the schema. The description only echoes the notion of boundedness via "bounded parts stock" without adding format, interaction, or defaulting details, so baseline 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 set: reads bounded parts stock, technician exposure, and transaction metadata for the authenticated workspace. The scope is clear enough that an agent knows what it will get, though no sibling tool is named or contrasted.

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?

"Use to inspect parts and inventory exposure in the connected business" gives an implied use case, but there is no when-not guidance, no prerequisites, and no mention of any alternative tool for parts or inventory data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources