Skip to main content
Glama
op-enny
by op-enny

fakestore_get_cart

Retrieve a specific shopping cart by its ID from the Fake Store API to view items, quantities, and totals for e-commerce testing or demonstration purposes.

Instructions

Get a single cart by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCart ID

Implementation Reference

  • Handler function that executes the core logic of fetching a single cart by ID from the Fake Store API, including input validation.
    export async function getCartById(args: { id: number }): Promise<Cart> {
      const { id } = args;
      validatePositiveInteger(id, 'Cart ID');
      return get<Cart>(`/carts/${id}`);
    }
  • Input schema definition for the fakestore_get_cart tool, specifying the required 'id' parameter.
    {
      name: 'fakestore_get_cart',
      description: 'Get a single cart by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Cart ID',
          },
        },
        required: ['id'],
      },
    },
  • src/index.ts:124-129 (registration)
    Registration and dispatch logic in the main CallToolRequest handler that matches the tool name and invokes the getCartById handler.
    if (name === 'fakestore_get_cart') {
      const result = await getCartById(args as { id: number });
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • src/index.ts:40-44 (registration)
    Tool listing handler that includes cartTools (containing the fakestore_get_cart schema) in the list of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [...productTools, ...cartTools, ...userTools],
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, it doesn't specify whether this requires authentication, what happens if the ID is invalid (e.g., returns null, throws error), or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 front-loads the core action ('Get a single cart by its ID') with zero wasted words. It's appropriately sized for a simple retrieval tool, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what the tool returns (e.g., cart details, error responses) or address potential complexities like authentication needs. For a retrieval tool with no structured output information, more context is needed to guide the agent fully.

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%, with the single parameter 'id' documented as 'Cart ID' in the schema. The description adds no additional meaning beyond this, such as format examples (e.g., numeric range) or context about valid IDs. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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') and resource ('a single cart by its ID'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'fakestore_get_carts' (plural) or 'fakestore_get_user_carts', which would require explicit differentiation to earn a 5.

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 like 'fakestore_get_carts' (for multiple carts) or 'fakestore_get_user_carts' (for user-specific carts). It lacks any context about prerequisites, error conditions, or typical use cases, leaving the agent with minimal usage direction.

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/op-enny/mcp-server-fakestore'

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