Chop MCP TypeScript
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obtener-setupD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose, while not described, is inherently distinct by being the sole option.
With a single tool, consistency cannot be assessed across multiple tools, but the tool name 'obtener-setup' uses a Spanish verb ('obtener') with a hyphenated noun, which is readable but lacks a pattern to evaluate against other tools. This places it in the middle of the scale due to the inability to judge consistency.
One tool is generally too few for most server purposes, as it suggests a very limited or trivial scope, making it difficult to perform meaningful operations. For a server named 'Chop MCP TypeScript', which might imply code or development tasks, a single tool feels insufficient and mismatched.
The server has only one tool with no description, making it impossible to infer the domain or assess coverage. With no clear purpose or additional tools, the surface is severely incomplete and will likely cause agent failures due to lack of functionality.