Skip to main content
Glama
Sign In
smart-retail-mcp

smart-retail-mcp

by eneidyscastellano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_current_stock

Retrieve current inventory levels for all products and supplier lead times to assess stock availability and plan replenishment.

Instructions

Obtiene los niveles actuales de inventario de todos los productos y los tiempos de entrega del proveedor.

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": "get_current_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Obtiene' and 'actuales' suggest a read-only, point-in-time snapshot, but there is no mention of authentication, response structure, data freshness guarantees, or error behavior. This is minimally informative but not misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence communicates the full scope of the tool without redundancy. Every word contributes meaning, and the main subject (inventory levels) appears early.

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 no-input read tool, the description is largely complete: it states what is returned and for whom. The only notable gap is the lack of an output schema or explicit description of the response format, but the conceptual content is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema already reflects that with an empty properties object. The description correctly focuses on what data is returned rather than explaining parameters, which are absent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Obtiene') and clearly identifies the resource: current inventory levels for all products plus supplier delivery times. This makes the tool's purpose distinct from sibling get_sales_velocity and create_ai_recommendation.

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?

The description implies the tool should be used when current inventory or supplier lead times are needed, but it does not explicitly state when to prefer it over alternatives or when not to use it. No comparison with sibling tools is provided.

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