Skip to main content
Glama
didacusdev

MCP Servers (OnePiece & Geolocalizar)

one_piece

Find detailed information about One Piece anime characters by entering their unique character ID.

Instructions

Herramienta para buscar informacion sobre personajes de One Piece

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId del personaje

Implementation Reference

  • Handler function for 'one_piece' tool. Fetches One Piece character data by ID from API or lists all characters if ID is a filter keyword like 'lista' or 'all'.
    async ({ id }) => {
        const filtros = ["lista", "personajes", "todos", "all", "*", "characters"];
        if(filtros.includes(id)) {
            try {
                const response = await axios.get(`https://onepieceapi-50cm.onrender.com/personajes`);
                const data = response.data;
                return {
                    content: [
                        {
                            type: 'text',
                            text: `Información de los personajes: ${JSON.stringify(data)}`,
                        }
                    ]
                };
            } catch (e) {
                return {
                    content: [
                        {
                            type: 'text',
                            text: `Error al buscar el personaje: ${e.message}`,
                        }
                    ],
                    isError: true
                };
            } 
        } else {
            try {
                const response = await axios.get(`https://onepieceapi-50cm.onrender.com/personaje/${id}`);
                const data = response.data;
                return {
                    content: [
                        {
                            type: 'text',
                            text: `Información del personaje: ${JSON.stringify(data)}`,
                        }
                    ]
                };
            } catch (e) {
                return {
                    content: [
                        {
                            type: 'text',
                            text: `Error al buscar el personaje: ${e.message}`,
                        }
                    ],
                    isError: true
                };
            } 
        }
        
    }
  • Input schema for 'one_piece' tool defining the required 'id' parameter as a string.
    {
        id: z.string().min(1, 'El id del personaje es requerido').describe('Id del personaje'),
    },
  • onePiece.ts:11-68 (registration)
    Registration of the 'one_piece' tool on the MCP server, including name, description, input schema, and handler.
    server.tool(
        'one_piece',
        'Herramienta para buscar informacion sobre personajes de One Piece',
        {
            id: z.string().min(1, 'El id del personaje es requerido').describe('Id del personaje'),
        },
        async ({ id }) => {
            const filtros = ["lista", "personajes", "todos", "all", "*", "characters"];
            if(filtros.includes(id)) {
                try {
                    const response = await axios.get(`https://onepieceapi-50cm.onrender.com/personajes`);
                    const data = response.data;
                    return {
                        content: [
                            {
                                type: 'text',
                                text: `Información de los personajes: ${JSON.stringify(data)}`,
                            }
                        ]
                    };
                } catch (e) {
                    return {
                        content: [
                            {
                                type: 'text',
                                text: `Error al buscar el personaje: ${e.message}`,
                            }
                        ],
                        isError: true
                    };
                } 
            } else {
                try {
                    const response = await axios.get(`https://onepieceapi-50cm.onrender.com/personaje/${id}`);
                    const data = response.data;
                    return {
                        content: [
                            {
                                type: 'text',
                                text: `Información del personaje: ${JSON.stringify(data)}`,
                            }
                        ]
                    };
                } catch (e) {
                    return {
                        content: [
                            {
                                type: 'text',
                                text: `Error al buscar el personaje: ${e.message}`,
                            }
                        ],
                        isError: true
                    };
                } 
            }
            
        }
    )
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. The description only states what the tool does (search for character information) but doesn't reveal any behavioral traits such as whether it's read-only or mutative, what format the information returns in, error conditions, rate limits, or authentication requirements. This leaves significant gaps in understanding how the tool behaves.

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, clear sentence in Spanish that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to quickly understand the core functionality.

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 that there are no annotations and no output schema, the description is insufficiently complete. It doesn't explain what kind of information is returned (e.g., character details, biography, abilities), the format of the response, or any error handling. For a search tool with no structured output documentation, the description should provide more context about the results.

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 input schema has 100% description coverage (the 'id' parameter is documented as 'Id del personaje'), so the baseline score is 3. The description doesn't add any additional meaning about the parameter beyond what the schema already provides—it doesn't explain what constitutes a valid character ID, provide examples, or clarify the search scope.

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 tool's purpose: 'buscar informacion sobre personajes de One Piece' (search for information about One Piece characters). It specifies both the verb (search) and resource (One Piece characters). However, since there are no sibling tools mentioned, we cannot assess differentiation from alternatives, so it cannot achieve a perfect 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. It doesn't mention any prerequisites, constraints, or contextual factors that would help an agent decide when this tool is appropriate. The absence of sibling tools means there's no explicit comparison, but the description still lacks basic usage context.

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/didacusdev/MCP-Servers'

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