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

fakestore_delete_user

Remove a user from the Fake Store API by specifying their ID to manage test data or clean up demo environments.

Instructions

Delete a user (simulation - does not persist)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID to delete

Implementation Reference

  • The core handler function that performs the user deletion by calling the Fake Store API's delete endpoint after validating the ID.
    export async function deleteUser(args: { id: number }): Promise<User> {
      const { id } = args;
      validatePositiveInteger(id, 'User ID');
      return del<User>(`/users/${id}`);
    }
  • The tool definition including name, description, and input schema for fakestore_delete_user.
    {
      name: 'fakestore_delete_user',
      description: 'Delete a user (simulation - does not persist)',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'User ID to delete',
          },
        },
        required: ['id'],
      },
    },
  • src/index.ts:224-229 (registration)
    The dispatch logic in the main tool call handler that routes fakestore_delete_user calls to the deleteUser function.
    if (name === 'fakestore_delete_user') {
      const result = await deleteUser(args as { id: number });
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior4/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. It clearly states this is a simulation that doesn't persist, which is crucial behavioral information about the tool's effect. However, it doesn't mention error handling, response format, or what happens when attempting to delete non-existent users.

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 extremely concise (6 words) and front-loaded with the essential information. Every word earns its place by conveying the action, resource, and critical behavioral constraint (simulation). No wasted words or unnecessary elaboration.

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 single-parameter deletion tool with no annotations and no output schema, the description provides good context by specifying it's a simulation. However, it doesn't explain what the tool returns (e.g., success/failure message, deleted user data) or address edge cases like invalid IDs, leaving some gaps in completeness.

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 schema description coverage is 100%, with the single parameter 'id' already documented as 'User ID to delete'. The description doesn't add any additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the specific action ('Delete') and resource ('a user'), and distinguishes it from siblings by specifying it's a simulation that doesn't persist. This provides precise differentiation from other tools like fakestore_delete_product or fakestore_delete_cart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context that this is a simulation tool, which implicitly suggests when to use it (for testing/development) versus when not to use it (for actual data deletion). However, it doesn't explicitly name alternatives or provide specific exclusion criteria beyond the simulation aspect.

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