Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

get_item

Retrieve inventory item details by ID to manage consignment and retail operations through the ConsignCloud API.

Instructions

Get details of a specific inventory item by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesItem ID (UUID)

Implementation Reference

  • src/server.ts:28-38 (registration)
    Tool registration defining the name, description, and input schema (requires 'id' string) for the 'get_item' MCP tool.
    {
      name: 'get_item',
      description: 'Get details of a specific inventory item by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Item ID (UUID)' },
        },
        required: ['id'],
      },
    },
  • MCP server tool handler: extracts 'id' from arguments, calls client.getItem(id), stringifies result as JSON, and returns as text content response.
    case 'get_item':
      return { content: [{ type: 'text', text: JSON.stringify(await client.getItem((args as any).id), null, 2) }] };
  • Core implementation of getItem: performs HTTP GET to `/items/${id}` API endpoint and converts the raw API response to Item type using currency conversion.
    async getItem(id: string): Promise<Item> {
      const response = await this.client.get(`/items/${id}`);
      return this.convertItemResponse(response.data);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get details' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data or just basic fields, or what happens with invalid IDs. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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?

The description is a single, efficient sentence that immediately conveys the core functionality. Every word earns its place with no redundancy or unnecessary elaboration. The structure is front-loaded with the essential information about what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read operation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'details' are returned, the format of the response, error conditions, or authentication requirements. Given the lack of structured metadata, the description should provide more context about the tool's behavior and output.

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?

The description mentions retrieving by 'ID' which aligns with the single 'id' parameter in the schema. Since schema description coverage is 100% (with the parameter already documented as 'Item ID (UUID)'), the description adds minimal value beyond what the schema provides. The baseline score of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 clearly states the verb ('Get details') and resource ('specific inventory item'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'list_items' by specifying retrieval of a single item by ID rather than listing multiple items. However, it doesn't explicitly differentiate from 'get_item_stats' which might also retrieve item-related data.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'get_item' over 'list_items' (for single vs multiple items), 'get_item_stats' (for detailed statistics vs basic details), or 'search_suggest' (for finding items when ID is unknown). There's also no mention of prerequisites like needing the item ID first.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/modellers/mcp-consigncloud'

If you have feedback or need assistance with the MCP directory API, please join our Discord server