Skip to main content
Glama
gregkop

Sketchfab MCP Server

by gregkop

sample-tool

Demonstrates how to interact with Sketchfab's 3D model platform through AI interfaces for searching, viewing details, and downloading 3D models.

Instructions

A sample tool for demonstration purposes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesInput parameter for the sample tool

Implementation Reference

  • The handler function for 'sample-tool' that takes an input string, prefixes it with 'Processed: ', and returns it as text content.
    async ({ input }) => {
      // Process the input
      const output = `Processed: ${input}`;
      
      // Return the result
      return {
        content: [
          {
            type: "text",
            text: output,
          },
        ],
      };
    }
  • Zod input schema for 'sample-tool' defining a single string parameter.
    {
      input: z.string().describe("Input parameter for the sample tool"),
    },
  • index.ts:256-276 (registration)
    Registration of 'sample-tool' via server.tool call, specifying name, description, schema, and handler function.
    server.tool(
      "sample-tool",
      "A sample tool for demonstration purposes",
      {
        input: z.string().describe("Input parameter for the sample tool"),
      },
      async ({ input }) => {
        // Process the input
        const output = `Processed: ${input}`;
        
        // Return the result
        return {
          content: [
            {
              type: "text",
              text: output,
            },
          ],
        };
      }
    );
Behavior1/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. The description offers no information about what the tool does, whether it's read-only or destructive, what permissions it requires, rate limits, or expected behavior. It fails to provide any behavioral context beyond the generic 'demonstration purposes' statement.

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

Conciseness3/5

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

The description is extremely concise (one sentence), but this brevity comes at the cost of being under-specified rather than efficiently informative. While it's technically concise, it doesn't provide enough substance to be truly helpful. The single sentence doesn't earn its place by adding meaningful value.

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

Completeness1/5

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

Given that this is a tool with one parameter but no annotations and no output schema, the description is completely inadequate. It doesn't explain what the tool does, when to use it, what behavior to expect, or what it returns. For a tool that presumably performs some function (given its siblings are all Sketchfab-related), this description fails to provide the necessary context.

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%, so the schema already documents the single 'input' parameter with its type and description. The tool description adds no additional meaning about parameters beyond what the schema provides. With complete schema coverage, 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.

Purpose2/5

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

The description 'A sample tool for demonstration purposes' is a tautology that restates the tool name 'sample-tool' without specifying what it actually does. It doesn't mention any specific verb or resource, nor does it distinguish this tool from its siblings (sketchfab-download, sketchfab-model-details, sketchfab-search). The description is vague about the tool's actual function.

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

Usage Guidelines1/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 its siblings or any alternatives. There's no mention of context, prerequisites, or exclusions. This leaves the agent with no information about appropriate usage scenarios.

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/gregkop/sketchfab-mcp-server'

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