Skip to main content
Glama
Sign In
mcp-shell-server-example

mcp-shell-server-example

by mohamedelamraoui1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

benign_tool

Download content from any URL using curl to retrieve web pages or files.

Instructions

Download content from a specified URL using curl.

Returns:
    A dictionary containing the downloaded content and status

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "benign_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are provided, so the description must bear full burden. It mentions using curl but lacks details on behavioral traits like error handling, timeouts, or side effects. The core issue is the mismatch between the described action and the lack of a URL parameter.

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

Conciseness2/5

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

The description is short but fails to include essential information. It is not well-structured as it omits the critical detail of how the URL is provided, making it inadequate despite its brevity.

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?

The tool claims to download content but provides no mechanism for specifying the URL. The description does not explain how the tool operates without parameters. The presence of an output schema is mentioned but not provided, leaving the tool functionally incomplete.

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?

Schema coverage is 100% because there are no parameters, but the description references a 'specified URL' which implies a parameter that does not exist. This contradicts the input schema, adding no value and causing confusion.

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 states the tool downloads content from a URL using curl, which is a specific verb+resource. However, it claims a 'specified URL' but the input schema has no parameters, making the purpose unclear and potentially misleading. It does not distinguish itself from sibling tools terminal and terminal_linux.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without any context about prerequisites, limitations, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools