Skip to main content
Glama
LucasDelgado

Chop MCP TypeScript

by LucasDelgado

obtener-setup

Retrieve setup information from Chop's system using a specific setup ID through the MCP server's REST API interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
setup_idYesEl id del setup a obtener

Implementation Reference

  • main.ts:17-32 (handler)
    The tool handler that takes a setup_id, fetches the setup data via HTTP GET from http://localhost:8080/backoffice/setup/${setup_id}, and returns the JSON-stringified response in a text content block.
    async ({ setup_id }) => {
        const url = `http://localhost:8080/backoffice/setup/${setup_id}`;
        
        const response = await axios.get<Setup>(url, {
            headers: {
                'Content-Type': 'application/json'
            }
        });
        
        return {
            content: [{
                type: 'text',
                text: JSON.stringify(response.data, null, 2)
            }]
        };
    }
  • main.ts:14-16 (schema)
    Input schema for the tool, requiring a numeric setup_id with description.
    {
        setup_id: z.number().describe('El id del setup a obtener')
    },
  • main.ts:12-33 (registration)
    Registration of the 'obtener-setup' tool on the MCP server, specifying the tool name, input schema using Zod, and the handler function.
    server.tool(
        "obtener-setup",
        {
            setup_id: z.number().describe('El id del setup a obtener')
        },
        async ({ setup_id }) => {
            const url = `http://localhost:8080/backoffice/setup/${setup_id}`;
            
            const response = await axios.get<Setup>(url, {
                headers: {
                    'Content-Type': 'application/json'
                }
            });
            
            return {
                content: [{
                    type: 'text',
                    text: JSON.stringify(response.data, null, 2)
                }]
            };
        }
    );
  • types.ts:1-13 (schema)
    TypeScript interface defining the Setup type used for typing the API response in the handler.
    export interface Setup {
        id: number;
        site_id: string;
        origin: string;
        entity_type: string;
        entity_type_id: string;
        collector_id: number;
        created_by: string;
        expired_at: string | null;
        internal_detail: InternalDetail;
        external_detail: Record<string, any> | null;
        created_at: string;
      }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/LucasDelgado/mcp-ts'

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