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

fakestore_get_product

Retrieve product details by ID from a mock e-commerce API for testing, demos, or learning MCP development.

Instructions

Get a single product by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID

Implementation Reference

  • Core handler function that validates the product ID and fetches the product from the FakeStore API using the get utility.
    export async function getProductById(args: { id: number }): Promise<Product> {
      const { id } = args;
      validatePositiveInteger(id, 'Product ID');
      return get<Product>(`/products/${id}`);
    }
  • Input schema definition for the fakestore_get_product tool, specifying the required 'id' parameter.
      name: 'fakestore_get_product',
      description: 'Get a single product by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Product ID',
          },
        },
        required: ['id'],
      },
    },
  • src/index.ts:61-66 (registration)
    Dispatch registration in the main tool handler that maps the tool name to the getProductById function and formats the response.
    if (name === 'fakestore_get_product') {
      const result = await getProductById(args as { id: number });
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' which implies a read operation, but doesn't disclose behavioral traits like error handling (e.g., what happens if ID doesn't exist), authentication needs, rate limits, or response format. This is a significant gap for a tool with no annotation coverage.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to scan and understand 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 no annotations and no output schema, the description is incomplete. It lacks details on return values, error conditions, or behavioral context needed for a tool that retrieves data. This is inadequate for a tool with no structured support.

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 parameter 'id' documented as 'Product ID'. The description adds no additional meaning beyond what the schema provides, such as ID format or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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 product'), specifying it's by ID. It distinguishes from sibling tools like 'fakestore_get_products' (plural) and 'fakestore_get_products_by_category', but doesn't explicitly contrast them. The purpose is specific and actionable.

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?

No guidance is provided on when to use this tool versus alternatives like 'fakestore_get_products' for multiple products or 'fakestore_get_products_by_category' for filtered lists. The description implies usage by ID but doesn't mention prerequisites or exclusions.

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